Bandan Das writes:
> There's too much going on in monitor_parse_command().
> Split up the arguments parsing bits into a separate function
> monitor_parse_arguments(). Let the original function check for
> command validity and sub-commands if any and return data (*cmd)
> that the newly introduced
Hi,
> On each boot, coreboot might decide to assign a different bus id to
> the extra roots (for example, if a device with a PCI bridge is
> inserted and it's bus allocation causes bus ids to shift).
> Technically, coreboot could even change the order extra buses are
> assigned bus ids, but does
Patch looks good to me, but it made me wonder about something. Please
find the question inline.
Eric Blake writes:
> We require a C99 compiler, so let's use 'bool' instead of 'int'
> when dealing with boolean values. There are few enough clients
> to fix them all in one pass.
>
> Signed-off-by
From: "Dr. David Alan Gilbert"
Signed-off-by: Dr. David Alan Gilbert
Signed-off-by: Juan Quintela
---
scripts/analyze-migration.py | 5 +
1 file changed, 5 insertions(+)
diff --git a/scripts/analyze-migration.py b/scripts/analyze-migration.py
index 0c8b22f..f6894be 100755
--- a/scripts/an
From: "Dr. David Alan Gilbert"
The header writing for device sections is open coded in
a few places, merge it into one.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Juan Quintela
Signed-off-by: Juan Quintela
---
migration/savevm.c | 72 +-
From: "Dr. David Alan Gilbert"
check the return value of the function it calls and error if it's non-0
Fixup qemu_rdma_init_one_block that is the only current caller,
and rdma_add_block the only function it calls using it.
Pass the name of the ramblock to the function; helps in debugging.
Sig
From: "Dr. David Alan Gilbert"
In postcopy we need the loadvm_handlers to be used in a couple
of different instances of the loadvm loop/routine, and thus
it can't be local any more.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: David Gibson
Reviewed-by: Juan Quintela
Signed-off-by: Juan
From: "Dr. David Alan Gilbert"
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Michael R. Hines
Signed-off-by: Juan Quintela
---
migration/rdma.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index 6c1e73f..48b3e64 100644
--- a/migration/rdma.c
+++
From: "Dr. David Alan Gilbert"
qemu_peek_buffer currently copies the data it reads into a buffer,
however a future patch wants access to the buffer without the copy,
hence rework to remove the copy to the layer above.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Amit Shah
Reviewed-by: Ju
From: "Dr. David Alan Gilbert"
Split qemu_savevm_state_begin to:
qemu_savevm_state_header That writes the initial file header.
qemu_savevm_state_beginThat sets up devices and does the first
device pass.
Used later in postcopy.
Signed-off-by: Dr. David Alan
From: "Dr. David Alan Gilbert"
The next patch adds section footers; but we don't want to
break migration compatibility so disable them on older
machine types
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Juan Quintela
Signed-off-by: Juan Quintela
---
hw/i386/pc_piix.c | 2 ++
From: "Dr. David Alan Gilbert"
There are currently lots of pieces of incoming migration state scattered
around, and postcopy is adding more, and it seems better to try and keep
it together.
allocate MIS in process_incoming_migration_co
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Amit Sh
From: "Dr. David Alan Gilbert"
RDMA has two data types that are named confusingly;
RDMALocalBlock (pointed to indirectly by local_ram_blocks)
RDMARemoteBlock (pointed to by block in RDMAContext)
RDMALocalBlocks, as the name suggests is a data strucuture that
represents the RDMAable RAM Blo
From: "Dr. David Alan Gilbert"
and use it in loadvm_state and ram_load.
Where ever it's used, check the return and error if it failed.
Minor: ram_load was using a 257 byte array for its string, the
maximum length is 255 bytes + 0 terminator, so fix to 256
Signed-off-by: Dr. David Alan G
For historic reasons, ram migration have been on arch_init.c. Just
split it into migration/ram.c, the same that happened with block.c.
There is only code movement, no changes altogether.
Signed-off-by: Juan Quintela
Reviewed-by: Eric Blake
---
MAINTAINERS |1 -
Makefile.
We create optional sections with this patch. But we already have
optional subsections. Instead of having two mechanism that do the
same, we can just generalize it.
For subsections we just change:
- Add a needed function to VMStateDescription
- Remove VMStateSubsection (after removal of the need
We assign the MIGRATION_STATUS_SETUP status in two places. Just in
succession. Just remove the second one.
Signed-off-by: Juan Quintela
Reviewed-by: Eric Blake
---
migration/migration.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/migration/migration.c b/migration/migration.c
index 7
From: "Dr. David Alan Gilbert"
Badly formatted migration streams can go undetected or produce
misleading errors due to a lock of checking at the end of sections.
In particular a section that adds an extra 0x00 at the end
causes what looks like a normal end of stream and thus doesn't produce
any e
From: Padmanabh Ratnakar
Qemu crashes when IPv6 address is specified for migration and access
to any RDMA uverbs device available on the system is blocked using cgroups.
Fix the crash by checking the return value of ibv_open_device routine.
Signed-off-by: Meghana Cheripady
Signed-off-by: Padman
To make changes easier, with the copy, I maintained almost all include
files. Now I remove the unnecessary ones on this patch. This compiles
on linux x64 with all architectures configured, and cross-compiles for
windows 32 and 64 bits.
Signed-off-by: Juan Quintela
Reviewed-by: Eric Blake
---
If anyone feels like adding himself to the list, just sent me a patch.
Signed-off-by: Juan Quintela
Reviewed-by: Eric Blake
---
migration/ram.c| 4
migration/savevm.c | 4
2 files changed, 8 insertions(+)
diff --git a/migration/ram.c b/migration/ram.c
index ff889ba..9db72a4 10064
Now, everything is in place.
Signed-off-by: Juan Quintela
Reviewed-by: Eric Blake
---
MAINTAINERS| 1 -
Makefile.target| 4 ++--
savevm.c => migration/savevm.c | 0
trace-events | 2 +-
4 files changed, 3 insertions(+), 4 deletions(-)
renam
This way, we will put savevm global state here, instead of lots of variables.
Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
---
migration/savevm.c | 51 ---
1 file changed, 28 insertions(+), 23 deletions(-)
diff --git a/migrati
From: zhanghailiang
There are two places that define 'len' variable, It's OK for compiling,
but makes it difficult for reading.
Remove the local one which defined in the inside 'while' loop.
Signed-off-by: zhanghailiang
Signed-off-by: Juan Quintela
---
migration/ram.c | 1 -
1 file changed,
Hi
[v2]
Just rebased.
[v1]
Here are the pull request, it includes:
- generic patches form postcopy that are reviewed (dave)
- generic patches form RDMA fixes that are reviewed (dave)
- patches form optional section reviewed (me)
- patches for migration events reviewed (me)
- fix RDMA and ipv6
On Tue, Jun 2, 2015 at 9:33 AM, Peter Maydell wrote:
> From: Eric Auger
>
> Device tree nodes for the platform bus and its children dynamic sysbus
> devices are added in a machine init done notifier. To load the dtb once,
> after those latter nodes are built and before ROM freeze, the actual
> ar
On Thu, Jun 11, 2015 at 9:58 AM, Peter Crosthwaite
wrote:
> On Tue, Jun 2, 2015 at 4:57 PM, Alistair Francis
> wrote:
>> On Tue, Jun 2, 2015 at 4:04 AM, Peter Crosthwaite
>> wrote:
>>> The CPUs currently supported by zynqmp are the APU (application
>>> processing unit) CPUs. There are other CPUs
On 2015-06-11 22:30, Hervé Poussineau wrote:
> This workarounds a bug in memory management.
>
> To reproduce the problem, try to start the Windows NT 4.0/MIPS installer.
> After loading some files, you should see a screen saying
> "To set up Windows NT now, press ENTER."
> However, you're welcomed
On 06/08/2015 11:21 AM, Vladimir Sementsov-Ogievskiy wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> Adds dirty-bitmaps feature to qcow2 format as specified in
> docs/specs/qcow2.txt
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> block/
On 2015-06-10 11:33, Pavel Dovgalyuk wrote:
> This patch fixes exception handling in MIPS.
> MIPS instructions generate several types of exceptions.
> When exception is generated, it breaks the execution of the current
> translation
> block. Implementation of the exceptions handling in MIPS does n
On 09/06/15 11:22, Stefan Hajnoczi wrote:
> On Tue, May 19, 2015 at 09:55:12PM +0100, Peter Maydell wrote:
>> On 19 May 2015 at 21:47, Mark Cave-Ayland
>> wrote:
>>> On 19/05/15 13:55, Andreas Färber wrote:
>>>
Am 19.05.2015 um 12:42 schrieb Stefan Hajnoczi:
> Ping. Should we stick with
On 2015-06-09 17:42, Leon Alrae wrote:
> Hi,
>
> This patchset adds large physical address support in MIPS, specifically:
> * eXtended Physical Addressing (XPA)
> * Large Physical Addressing (LPA)
>
> XPA and LPA are enabled in MIPS32R5-generic and MIPS64R6-generic cores
> respectively.
>
> The
11.06.2015 23:46, Apollon Oikonomopoulos wrote:
> On 15:12 Wed 03 Jun , Apollon Oikonomopoulos wrote:
>> Any ideas?
>
> As far as I understand, there is an issue when reading the MSR on the
> incoming side: there is a KVM_SET_MSRS vcpu ioctl issued by the main
> thread during initialization,
On 06/08/2015 11:21 AM, Vladimir Sementsov-Ogievskiy wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> The patch adds the following command line option:
>
> -dirty-bitmap [option1=val1][,option2=val2]...
> Available options are:
> name The name for the bitmap (necessary).
>
>
On 15:12 Wed 03 Jun , Apollon Oikonomopoulos wrote:
> Any ideas?
As far as I understand, there is an issue when reading the MSR on the
incoming side: there is a KVM_SET_MSRS vcpu ioctl issued by the main
thread during initialization, that causes the initial vCPU steal time
value to be set u
This workarounds a bug in memory management.
To reproduce the problem, try to start the Windows NT 4.0/MIPS installer.
After loading some files, you should see a screen saying
"To set up Windows NT now, press ENTER."
However, you're welcomed with an IRQL_NOT_LESS_OR_EQUAL bugcheck or an
Unknown Ha
The load/store API is not scalable when bitmaps are 1 MB or larger.
For example, a 500 GB disk image with 64 KB granularity requires a 1 MB
bitmap. If a guest has several disk images of this size, then multiple
megabytes must be read to start the guest and written out to shut down
the guest.
By
On Thu, Jun 11, 2015 at 08:34:56PM +0200, Laszlo Ersek wrote:
> On 06/11/15 19:46, Marcel Apfelbaum wrote:
> > On 06/11/2015 07:54 PM, Kevin O'Connor wrote:
> >> On real machines, the firmware assigns the 4 - it's not a physical
> >> address; it's a logical address (like all bus numbers in PCI). T
On Thu, Jun 11, 2015 at 08:46:01PM +0300, Marcel Apfelbaum wrote:
> On 06/11/2015 07:54 PM, Kevin O'Connor wrote:
> >On real machines, the firmware assigns the 4 - it's not a physical
> >address; it's a logical address (like all bus numbers in PCI). The
> >firmware might assign a totally different
On 06/11/2015 01:58 PM, Dr. David Alan Gilbert wrote:
* Michael R. Hines (mrhi...@linux.vnet.ibm.com) wrote:
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
The 'offset' field in RDMACompress and 'current_addr' field
in RDMARegister are commented as
Hi Artyom,
Le 11/06/2015 10:02, Artyom Tarasenko a écrit :
Hi Hervé,
On Wed, Jun 10, 2015 at 11:18 PM, Hervé Poussineau wrote:
Hi,
This patchset adds the emulation of the IBM RS/6000 7020 (40p).
Well done! Congratulations on a good job!
The real machine is
able to run AIX (up to 4.3.3),
* Michael R. Hines (mrhi...@linux.vnet.ibm.com) wrote:
> On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
> >From: "Dr. David Alan Gilbert"
> >
> >The 'offset' field in RDMACompress and 'current_addr' field
> >in RDMARegister are commented as being offsets within a particular
> >RAMBloc
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
Use the order of incoming RAMBlocks from the source to record
an index number; that then allows us to sort the destination
local RAMBlock list to match the source.
Now that the RAMBlocks are known to be
* Michael R. Hines (mrhi...@linux.vnet.ibm.com) wrote:
> On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
> >From: "Dr. David Alan Gilbert"
> >
> >RDMA uses a hash from block offset->RAM Block; this isn't needed
> >on the destination, and it becomes harder to maintain after the next
> >
* Michael R. Hines (mrhi...@linux.vnet.ibm.com) wrote:
> On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
> >From: "Dr. David Alan Gilbert"
> >
> >We need the names of RAMBlocks as they're loaded for RDMA,
> >reuse a slightly modified ram_control_load_hook:
> > a) Pass a 'data' parame
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
RDMA uses a hash from block offset->RAM Block; this isn't needed
on the destination, and it becomes harder to maintain after the next
patch in the series that sorts the block list.
Split the hash so that
* Michael R. Hines (mrhi...@linux.vnet.ibm.com) wrote:
> On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
> >From: "Dr. David Alan Gilbert"
> >
> >In the next patch we remove the hash on the destination,
> >rdma_delete_block does two things with the hash which can be avoided:
> > a) T
On 06/11/15 18:48, Kevin O'Connor wrote:
> On Thu, Jun 11, 2015 at 04:35:33PM +0200, Laszlo Ersek wrote:
>> On 06/11/15 15:58, Kevin O'Connor wrote:
>>> On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pc
* Michael R. Hines (mrhi...@linux.vnet.ibm.com) wrote:
> On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
> >From: "Dr. David Alan Gilbert"
> >
> >A couple of typo fixes.
> >
> >Signed-off-by: Dr. David Alan Gilbert
> >---
> > migration/rdma.c | 6 +++---
> > trace-events | 4 ++--
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
In the next patch we remove the hash on the destination,
rdma_delete_block does two things with the hash which can be avoided:
a) The caller passes the offset and rdma_delete_block looks it up
in
On 06/11/15 19:46, Marcel Apfelbaum wrote:
> On 06/11/2015 07:54 PM, Kevin O'Connor wrote:
>> On Thu, Jun 11, 2015 at 05:36:06PM +0300, Marcel Apfelbaum wrote:
>>> On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
> On 06/11/201
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
We need the names of RAMBlocks as they're loaded for RDMA,
reuse a slightly modified ram_control_load_hook:
a) Pass a 'data' parameter to use for the name in the block-reg
case
b) Only some ho
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
The 'offset' field in RDMACompress and 'current_addr' field
in RDMARegister are commented as being offsets within a particular
RAMBlock, however they appear to actually be offsets within the
ram_addr_t sp
On 06/11/2015 04:41 AM, Fam Zheng wrote:
> On Fri, 05/22 13:35, Fam Zheng wrote:
>
> Ping :)
>
> Fam
>
>>
>>
>> Fam Zheng (2):
>> Makefile: Fix "make cscope TAGS"
>> Makefile: Add "make ctags"
>>
>> Makefile | 20 +++-
>> 1 file changed, 15 insertions(+), 5 deletions(-)
>>
On Thu, 28 May 2015 16:18:41 -0400
Luiz Capitulino wrote:
> On Mon, 18 May 2015 13:22:16 +0200
> hw.clau...@gmail.com wrote:
>
> > From: Claudio Fontana
> >
> > This is the latest iteration of the memory search patch,
> > including a trivial replacement for the memmem function for systems
> >
On Thu, 28 May 2015 15:54:12 -0400
Luiz Capitulino wrote:
> On Fri, 15 May 2015 16:24:58 -0600
> Eric Blake wrote:
>
> > Passing around an 'int' for a QBool type is weird, when we already
> > use a C99 compiler and have a sane 'bool' that does just fine.
> >
> > I half-debated sending this thr
On Mon, 08 Jun 2015 10:53:23 +0200
Markus Armbruster wrote:
> Copying HMP maintainer Luiz.
>
> Series
> Reviewed-by: Markus Armbruster
>
> Bandan, thanks for your patience.
>
> Luiz, my monitor/QMP queue is currently empty, but if it fills up before
> you get around to doing a monitor/HMP pul
On Sun, 24 May 2015 14:20:39 -0700
Peter Crosthwaite wrote:
> Neither the monitor or disassembly core has a good reason to navigate from an
> env pointer to a cpu pointer. Disas should not need env awarness at all, that
> is removed in P2.
>
> The monitor is trickier, the env is still needed by
On 06/11/2015 12:17 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
A couple of typo fixes.
Signed-off-by: Dr. David Alan Gilbert
---
migration/rdma.c | 6 +++---
trace-events | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/migration/rdm
On 06/11/2015 07:54 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 05:36:06PM +0300, Marcel Apfelbaum wrote:
On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at
From: "Dr. David Alan Gilbert"
If the number of RAMBlocks was different on the source from the
destination, QEMU would hang waiting for a disconnect on the source
and wouldn't release from that hang until the destination was manually
killed.
Mark the stream as being in error, this causes the des
From: "Dr. David Alan Gilbert"
We need the names of RAMBlocks as they're loaded for RDMA,
reuse a slightly modified ram_control_load_hook:
a) Pass a 'data' parameter to use for the name in the block-reg
case
b) Only some hook types now require the presence of a hook function.
Signed-off
From: "Dr. David Alan Gilbert"
In the next patch we remove the hash on the destination,
rdma_delete_block does two things with the hash which can be avoided:
a) The caller passes the offset and rdma_delete_block looks it up
in the hash; fixed by getting the caller to pass the block
b) Th
From: "Dr. David Alan Gilbert"
A couple of typo fixes.
Signed-off-by: Dr. David Alan Gilbert
---
migration/rdma.c | 6 +++---
trace-events | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index bc73ff8..44ed996 100644
--- a/migrat
From: "Dr. David Alan Gilbert"
The 'offset' field in RDMACompress and 'current_addr' field
in RDMARegister are commented as being offsets within a particular
RAMBlock, however they appear to actually be offsets within the
ram_addr_t space.
The code currently assumes that the offsets on the sourc
From: "Dr. David Alan Gilbert"
Use the order of incoming RAMBlocks from the source to record
an index number; that then allows us to sort the destination
local RAMBlock list to match the source.
Now that the RAMBlocks are known to be in the same order, this
simplifies the RDMA Registration step
From: "Dr. David Alan Gilbert"
RDMA uses a hash from block offset->RAM Block; this isn't needed
on the destination, and it becomes harder to maintain after the next
patch in the series that sorts the block list.
Split the hash so that it's only generated on the source.
Signed-off-by: Dr. David
From: "Dr. David Alan Gilbert"
In a later patch the block name will be used to match up two views
of the block list. Keep a copy of the block name with the local block
list.
(At some point it could be argued that it would be best just to let
migration see the innards of RAMBlock and avoid the n
From: "Dr. David Alan Gilbert"
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Michael R. Hines
---
migration/rdma.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index 38e5f44..bc73ff8 100644
--- a/migration/rdma.c
+++ b/migration/rdma.c
@@ -2445,7
From: "Dr. David Alan Gilbert"
check the return value of the function it calls and error if it's non-0
Fixup qemu_rdma_init_one_block that is the only current caller,
and rdma_add_block the only function it calls using it.
Pass the name of the ramblock to the function; helps in debugging.
Sig
From: "Dr. David Alan Gilbert"
Perform some basic (but probably not complete) sanity checking on
requests from the RDMA source.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Michael R. Hines
---
migration/rdma.c | 30 ++
1 file changed, 30 insertions(+)
diff
From: "Dr. David Alan Gilbert"
RDMA migration currently relies on the source and destination RAMBlocks
having the same offsets within ram_addr_t space; unfortunately that's
just not true when:
a) You hotplug on the source but then create the device on the command line
on the destination.
From: "Dr. David Alan Gilbert"
RDMA has two data types that are named confusingly;
RDMALocalBlock (pointed to indirectly by local_ram_blocks)
RDMARemoteBlock (pointed to by block in RDMAContext)
RDMALocalBlocks, as the name suggests is a data strucuture that
represents the RDMAable RAM Blo
Hello Igor,
the current hotplug code for dimms effectively prohibiting a
successful migration for VM if memory was added after startup:
- start a VM with certain amount of empty memory slots,
- add some dimms and online them in guest (I am transitioning from 2
to 16G with 512Mb DIMMs),
- migrate
On Thu, Jun 11, 2015 at 05:36:06PM +0300, Marcel Apfelbaum wrote:
> On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
> >On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
> >>On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
> >>>On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wr
On Thu, Jun 11, 2015 at 04:35:33PM +0200, Laszlo Ersek wrote:
> On 06/11/15 15:58, Kevin O'Connor wrote:
> > On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
> >> The fixes solves the following issue:
> >> The PXB device exposes a new pci root bridge with the
> >> fw path: /pci-r
From: Xu Wang
Let's introduce a general "inject_nmi()" function that doesn't rely on the cpu
index of the monitor, but uses cpu index 0 as default (except for x86).
This function can then later be used from a non-monitor context.
Signed-off-by: Xu Wang
Reviewed-by: David Hildenbrand
CC: Alexey
From: Xu Wang
We will introduce a new watchdog for s390x. Lets adopt
qemu-options.hx to allow more watchdog devices.
Signed-off-by: Xu Wang
Reviewed-by: David Hildenbrand
Signed-off-by: Christian Borntraeger
[split out qemu-option.hx base changes]
---
qemu-options.hx | 23 ++-
On 06/11/2015 06:49 AM, Vladimir Sementsov-Ogievskiy wrote:
> On 11.06.2015 02:42, John Snow wrote:
>>
>> On 06/08/2015 11:21 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> From: Vladimir Sementsov-Ogievskiy
>>>
>>> Signed-off-by: Vladimir Sementsov-Ogievskiy
>>> ---
>>> block/qcow2-dirty-bitmap
On 06/11/2015 06:25 AM, Vladimir Sementsov-Ogievskiy wrote:
> On 10.06.2015 18:34, Kevin Wolf wrote:
>> Am 08.06.2015 um 17:21 hat Vladimir Sementsov-Ogievskiy geschrieben:
>>> From: Vladimir Sementsov-Ogievskiy
>>>
>>> Persistent dirty bitmaps will be saved into qcow2 files. It may be used
>>>
From: Xu Wang
This patch introduces a new diag288 watchdog device that will, just like
other watchdogs, monitor a guest and take corresponding actions when it
detects that the guest is not responding.
diag288 is s390x specific. The wiring to s390x KVM will be done in
separate patches.
Signed-of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/11/2015 09:03 AM, Stefan Hajnoczi wrote:
> On Thu, Jun 11, 2015 at 01:19:24PM +0300, Vladimir
> Sementsov-Ogievskiy wrote:
>> On 10.06.2015 16:24, Stefan Hajnoczi wrote:
>>> On Wed, Jun 10, 2015 at 11:19:30AM +0300, Vladimir
>>> Sementsov-Ogi
From: Xu Wang
Intercept the diag288 requests from kvm guests, and hand the
requested command to the diag288 watchdog device for further
handling.
Signed-off-by: Xu Wang
Reviewed-by: David Hildenbrand
Signed-off-by: Christian Borntraeger
---
target-s390x/cpu.h | 1 +
target-s390x/kvm
This is the reworked patch set for the s390 diag288 watchdog.
The previous version was posted bny Cornelia in this thread:
https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg01950.html
This patch set should address all review comments.
If there are no blockers, pull request is planned for ne
From: Xu Wang
Add vmstate structure to keep state and data during migration.
Signed-off-by: Xu Wang
Reviewed-by: David Hildenbrand
Signed-off-by: Christian Borntraeger
---
hw/watchdog/wdt_diag288.c | 12
1 file changed, 12 insertions(+)
diff --git a/hw/watchdog/wdt_diag288.c b/
From: Mao Chuan Li
This patch allows QEMU to inject a NMI into a guest when the
watchdog expires.
Signed-off-by: Mao Chuan Li
Reviewed-by: David Hildenbrand
CC: Eric Blake
CC: Markus Armbruster
Signed-off-by: Christian Borntraeger
---
hw/watchdog/watchdog.c | 10 ++
qapi-schema.jso
Hi Gerd,
Based on the current implementation of 'usb_host_open' in
hw/usb/host-libusb.c,
When user performs usb_add, The usb device will be detached from kernel
first, Then be checked for speed mismatch second.
If it found speed mismatch, The usb device isn't attached to guest, But
the usb d
On 11 June 2015 at 12:57, Michael S. Tsirkin wrote:
> The following changes since commit 309750fad51f17d1ec6195c5d8ad7d741596ddb6:
>
> vhost: logs sharing (2015-06-04 12:44:49 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_ups
It seems that the problem is from the code itself.
If I call vhost_dev_start() in set_status() (in qemu), when the status
changes to VIRTIO_CONFIG_S_DRIVER_OK, only the communication path from
guest to vhost works.
In another scenario I send a message from guest to qemu, and the vq
handler in qemu
On 06/11/15 16:36, Marcel Apfelbaum wrote:
> On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
>> On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
>>> On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
> The fixes so
On 06/11/2015 05:24 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pc
On 06/11/15 15:58, Kevin O'Connor wrote:
> On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
>> The fixes solves the following issue:
>> The PXB device exposes a new pci root bridge with the
>> fw path: /pci-root@4/..., in which 4 is the root bus number.
>> Before this patch the f
stream' into
> staging (2015-06-08 15:57:41 +0100)
>
> are available in the git repository at:
>
>
> git://git.kraxel.org/qemu tags/pull-sdl-20150611-1
>
> for you to fetch changes up to 08d49df0dbaacc220a099dbfb644e1dc0eda57be:
>
> sdl2: fix crash in handl
Is there something I need to install (kernel module or something like
that) so that the virtio guest receives signals from vhost?
The communication from and to qemu works (I can send a message from
guest to qemu, and I can send a message from qemu to guest), and I can
send a message from guest to v
On Thu, Jun 11, 2015 at 05:12:33PM +0300, Marcel Apfelbaum wrote:
> On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
> >On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
> >>The fixes solves the following issue:
> >>The PXB device exposes a new pci root bridge with the
> >>fw path: /
On 11 May 2015 at 07:53, Gerd Hoffmann wrote:
> On So, 2015-05-10 at 23:51 +0100, Peter Maydell wrote:
>> So looking at the code in ui/console.c that implements our
>> virtual consoles, the scrolling is hooked up to the keycodes
>> QEMU_KEY_CTRL_{UP,DOWN,PAGEUP,PAGEDOWN}. These only seem
>> to be
On 06/11/2015 04:58 PM, Kevin O'Connor wrote:
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
The fixes solves the following issue:
The PXB device exposes a new pci root bridge with the
fw path: /pci-root@4/..., in which 4 is the root bus number.
Before this patch the fw path
On 11 June 2015 at 09:44, Eric Auger wrote:
> g_malloc0_n() is introduced since glib-2.24 while QEMU currently
> requires glib-2.22. This may cause a link error on some distributions.
>
> Signed-off-by: Eric Auger
>
> ---
>
> v1 -> v2:
> - replace g_malloc0 by g_new0
> ---
> hw/vfio/platform.c |
Signed-off-by: Frediano Ziglio
---
hw/display/qxl-logger.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/hw/display/qxl-logger.c b/hw/display/qxl-logger.c
index c900c2c..d944d3f 100644
--- a/hw/display/qxl-logger.c
+++ b/hw/display/qxl-logger.c
@@ -22,7 +22,
On Thu, Jun 11, 2015 at 04:37:08PM +0300, Marcel Apfelbaum wrote:
> The fixes solves the following issue:
> The PXB device exposes a new pci root bridge with the
> fw path: /pci-root@4/..., in which 4 is the root bus number.
> Before this patch the fw path was wrongly computed:
> /pci-root@1/
1 - 100 of 231 matches
Mail list logo
