* Alex Bennée (alex.ben...@linaro.org) wrote:
>
> Achilles Benetopoulos writes:
>
> > I am interested in working on the BiteSized Task mentioned in the
> > subject line. However, I have a question: Since the current behaviour
> > of qemu_thread_create is to fail in the case of an error, then it
On 03/16/2017 01:25 PM, Kevin Wolf wrote:
> Am 16.03.2017 um 01:46 hat John Snow geschrieben:
>> Signed-off-by: John Snow
>>
>> ---
>>
>> RFC questions:
>>
>> - Does the presence of blk->quiesce_counter relieve the burden of needing
>> blk->public.io_limits_disabled? I could probably eliminate
Hi all,
This patch series implements a new transport for 9pfs, aimed at Xen
systems.
The transport is based on a traditional Xen frontend and backend drivers
pair. This patch series implements the backend, which typically runs in
Dom0. I sent another series to implement the frontend in Linux
(htt
Introduce the Xen 9pfs backend: add struct XenDevOps to register as a
Xen backend and add struct V9fsTransport to register as v9fs transport.
All functions are empty stubs for now.
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Ane
Use the new type in virtio-9p-device.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg Kurz
---
hw/9pfs/9p.h | 6 ++
hw/9pfs/virtio-9p-device.c | 6 +-
2 files changed, 7 insertions(+), 5 deletions(-)
diff
Do not use the ring.h header installed on the system. Instead, import
the header into the QEMU codebase. This avoids problems when QEMU is
built against a Xen version too old to provide all the ring macros.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
---
NB
Write the limits of the backend to xenstore. Connect to the frontend.
Upon connection, allocate the rings according to the protocol
specification.
Initialize a QEMUBH to schedule work upon receiving an event channel
notification from the frontend.
Signed-off-by: Stefano Stabellini
CC: anthony.pe
Once a request is completed, xen_9pfs_push_and_notify gets called. In
xen_9pfs_push_and_notify, update the indexes (data has already been
copied to the sg by the common code) and send a notification to the
frontend.
Schedule the bottom-half to check if we already have any other requests
pending.
* Juan Quintela (quint...@redhat.com) wrote:
> Signed-off-by: Juan Quintela
> ---
> migration/ram.c | 12 +++-
> 1 file changed, 7 insertions(+), 5 deletions(-)
Reviewed-by: Dr. David Alan Gilbert
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 8caeb4f..234bdba 100644
> ---
Change Makefile.objs to use CONFIG_XEN instead of CONFIG_XEN_BACKEND, so
that the Xen backends are only built for targets that support Xen.
Set CONFIG_XEN in the toplevel Makefile to ensure that files that are
built only once pick up Xen support properly.
Signed-off-by: Stefano Stabellini
CC: gr
> > memory_region_finalize.
> > Let me know if you think otherwise.
>
> Yes, you can replace memory_region_del_subregion in
> memory_region_finalize
> with special code that does
>
> assert(!mr->enabled);
> assert(subregion->container == mr);
> subregion->container = NULL;
> QTAIL
Implement xen_9pfs_init_in/out_iov_from_pdu and
xen_9pfs_pdu_vmarshal/vunmarshall by creating new sg pointing to the
data on the ring.
This is safe as we only handle one request per ring at any given time.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: An
Upon receiving an event channel notification from the frontend, schedule
the bottom half. From the bottom half, read one request from the ring,
create a pdu and call pdu_submit to handle it.
For now, only handle one request per ring at a time.
Signed-off-by: Stefano Stabellini
CC: anthony.per...
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg Kurz
---
hw/9pfs/Makefile.objs| 1 +
hw/xen/xen_backend.c | 3 +++
include/hw/xen/xen_backend.h | 3 +++
3 files changed, 7 insertions(+)
di
* Juan Quintela (quint...@redhat.com) wrote:
> Once there, remove the now unused AccountingInfo struct and var.
>
> Signed-off-by: Juan Quintela
> ---
> migration/ram.c | 21 +
> 1 file changed, 5 insertions(+), 16 deletions(-)
>
> diff --git a/migration/ram.c b/migration/ra
* Juan Quintela (quint...@redhat.com) wrote:
> And then init only things that are not zero by default.
>
> Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
> ---
> migration/ram.c | 25 +++--
> 1 file changed, 3 insertions(+), 22 deletions(-)
>
> diff --gi
On Thu, 16 Mar 2017, Juergen Gross wrote:
> Today qemu is using e.g. the value 480 for Xen version 4.8.0. As some
> Xen version tests are using ">" relations this scheme will lead to
> problems when Xen version 4.10.0 is being reached.
>
> Instead of the 3 digit schem use a 5 digit scheme (e.g. 40
On Thu, 16 Mar 2017, Juergen Gross wrote:
> Instead of trying to guess the Xen version to use by compiling various
> test programs first just ask the system via pkg-config. Only if it
> can't return the version fall back to the test program scheme.
That's OK, but why did you remove the Xen unstabl
* Juan Quintela (quint...@redhat.com) wrote:
> Signed-off-by: Juan Quintela
> ---
> migration/ram.c | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 7f56b5f..c14293c 100644
> --- a/migration/ram.c
> +++ b/migration/
> Am 16.03.2017 um 17:18 schrieb Paolo Bonzini :
>
>
>
> On 16/03/2017 17:02, Peter Lieven wrote:
>> commit 3c80ca15 fixed a deadlock scenarion with nested aio_poll invocations.
>>
>> However, the rescheduling of the completion BH introcuded unnecessary
>> spinning
>> in the main-loop. On ver
The purpose of this shim is to allow us to pause pre-started jobs.
The purpose of *that* is to allow us to buffer a pause request that
will be able to take effect before the job ever does any work, allowing
us to create jobs during a quiescent state (under which they will be
automatically paused),
Allow block backends to forward drain requests to their devices/users.
The initial intended purpose for this patch is to allow BBs to forward
requests along to BlockJobs, which will want to pause if their associated
BB has entered a drained region.
Signed-off-by: John Snow
---
block/block-backen
This lets us hook into drained_begin and drained_end requests from the
backend level, which is particularly useful for making sure that all
jobs associated with a particular node (whether the source or the target)
receive a drain request.
Suggested-by: Kevin Wolf
Signed-off-by: John Snow
---
bl
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1367369#c8
It's possible to wedge QEMU if the guest tries to reset a virtio-pci
device as QEMU is also using the drive for a blockjob. This patchset
aims to allow us to safely pause/resume jobs attached to individual
nodes in a manner similar
On Thu, 16 Mar 2017 15:08:46 +0800 Wei Wang wrote:
> From: Liang Li
>
> This patch adds a function to provides a snapshot of the present system
> unused pages. An important usage of this function is to provide the
> unsused pages to the Live migration thread, which skips the transfer of
> those
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v2 0/3] block: pause block jobs for
bdrv_drain_begin/end
Message-id: 20170316212351.13797-1-js...@redhat.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=bas
On 03/16/2017 09:09 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
last_seen_block, last_sent_block, last_offset, last_version and
ram_bulk_stage are globals that are really related together.
Signed-off-by: Juan Quintela
---
migration/ram.c | 136 ++
On 03/16/2017 09:21 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Philippe Mathieu-Daudé
---
migration/ram.c | 22 +++---
1 file changed, 11 insertions(+), 11
On 03/16/2017 09:20 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
We need to add a parameter to several functions to make this work.
Signed-off-by: Juan Quintela
---
migration/ram.c | 23 ---
1 file changed, 12 insertions(+), 11 deletions(-
On 03/16/2017 09:23 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Philippe Mathieu-Daudé
(This series could be fewer patches...)
---
migration/ram.c | 13 +++--
1 f
On 03/16/2017 09:21 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Philippe Mathieu-Daudé
---
migration/ram.c | 20 +++-
1 file changed, 11 insertions(+), 9 de
On 03/16/2017 09:24 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
---
migration/ram.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index b13d2d5..ae077c5 100644
--- a
On 03/16/2017 09:22 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Philippe Mathieu-Daudé
---
migration/ram.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(
On 03/16/2017 05:04 PM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
---
migration/ram.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Philippe Mathieu-Daudé
On 03/16/2017 09:26 AM, Dr. David Alan Gilbert wrote:
* Juan Quintela (quint...@redhat.com) wrote:
Signed-off-by: Juan Quintela
---
migration/ram.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index ae077c5..6cdad06 100644
On Tue, Mar 14, 2017 at 8:36 AM, Fam Zheng wrote:
> diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
> index e7466d3..4939f1f 100644
> --- a/hw/scsi/virtio-scsi.c
> +++ b/hw/scsi/virtio-scsi.c
> ...
> bool virtio_scsi_handle_event_vq(VirtIOSCSI *s, VirtQueue *vq)
> {
> -virtio_scsi
On Tue, Mar 14, 2017 at 8:36 AM, Fam Zheng wrote:
> After the AioContext lock push down, there is a race between
> virtio_scsi_dataplane_start and those "assert(s->ctx &&
> s->dataplane_started)", because the latter doesn't isn't wrapped in
> aio_context_acquire.
>
> Reproducer is simply booting a
On Mon, Mar 13, 2017 at 2:57 AM, Daniel P. Berrange wrote:
> On Tue, Mar 07, 2017 at 05:27:55PM -0800, ashish mittal wrote:
>> Thanks! There is one more input I need some help with!
>>
>> VxHS network library opens a fixed number of connection channels to a
>> given host, and all the vdisks (that
On Thu, Mar 16, 2017 at 03:08:46PM +0800, Wei Wang wrote:
> +/*
> + * The record_unused_pages() function is used to record the system unused
> + * pages. The unused pages can be skipped to transfer during live migration.
> + * Though the unused pages are dynamically changing, dirty page logging
> +
On Thu, 03/16 16:48, Ed Swierk wrote:
> On Tue, Mar 14, 2017 at 8:36 AM, Fam Zheng wrote:
> > diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
> > index e7466d3..4939f1f 100644
> > --- a/hw/scsi/virtio-scsi.c
> > +++ b/hw/scsi/virtio-scsi.c
> > ...
> > bool virtio_scsi_handle_event_vq(V
On Thu, Mar 16, 2017 at 03:08:47PM +0800, Wei Wang wrote:
> From: Liang Li
>
> Add a new vq, host request vq. The host uses the vq to send
> requests to the guest. Upon getting a request, the guest responds
> what the host needs via this vq.
>
> The patch implements the request of getting the un
Signed-off-by: Fam Zheng
---
block.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block.c b/block.c
index cb57370..6621167 100644
--- a/block.c
+++ b/block.c
@@ -2025,6 +2025,7 @@ int bdrv_open_backing_file(BlockDriverState *bs, QDict
*parent_options,
bdrv_set_backing_hd(bs, backing_
On Thu, Mar 16, 2017 at 02:52:17PM +0100, Cédric Le Goater wrote:
> On 03/15/2017 07:16 AM, David Gibson wrote:
> > On Wed, Mar 08, 2017 at 11:52:49AM +0100, Cédric Le Goater wrote:
> >> From: Benjamin Herrenschmidt
> >>
> >> The PSI (Processor Service Interface) Controller is one of the engines
>
hi
http://git.qemu-project.org/?p=qemu.gita=blobf=docs/COLO-FT.txth=e289be2f419578645475b36861e4303ff624cb0fhb=HEAD
docs/COLO-FT
138 {'execute':'qmp_capabilities'}
139 { 'execute': 'nbd-server-start',
140 'arguments': {'addr': {'type': 'inet', 'data': {'host': 'xx.xx.xx.xx',
'port
BDRVReplicationState.replication_state is a name with a bit of
duplication, plus it could be an enum like BDRVReplicationState.mode,
which is be more readable and also more straightforward in a debuuger.
Rename it, and improve the type while at it.
Signed-off-by: Fam Zheng
---
block/replication
在 2017/3/16 16:01, Juan Quintela 写道:
QingFeng Hao wrote:
This problem affects s390x only if we are running without KVM.
Basically, S390CPU.irqstate is unused if we do not use KVM,
and thus no buffer is allocated.
This causes size=0, first_elem=NULL and n_elems=1 in
vmstate_load_state and vmst
For future code reuse purpose, this decouples the cio code with
the ccw device specific parts from ccw_device_cancel_halt_clear,
and makes a new common I/O interface named cio_cancel_halt_clear.
Reviewed-by: Pierre Morel
Signed-off-by: Dong Jia Shi
Cc: Sebastian Ott
Cc: Peter Oberparleiter
---
Define vfio-ccw device API strings. CCW vendor driver using mediated
device framework should use this string for device_api attribute.
Reviewed-by: Pierre Morel
Signed-off-by: Dong Jia Shi
---
include/uapi/linux/vfio.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/vfio.
vfio-ccw: the basic infrastructure
==
Introduction
Here we describe the vfio support for I/O subchannel devices for
Linux/s390. Motivation for vfio-ccw is to passthrough subchannels to a
virtual machine, while vfio is the means.
Different than other h
To make vfio support subchannel devices, we need to leverage the
mediated device framework to create a mediated device for the
subchannel device.
This registers the subchannel device to the mediated device
framework during probe to enable mediated device creation.
Reviewed-by: Pierre Morel
Signe
To provide user-space a set of interfaces to:
1. pass in a ccw program to perform an I/O operation.
2. read back I/O results of the completed I/O operations.
We introduce an MMIO region for the vfio-ccw device here.
This region is defined to content:
1. areas to store arguments that an ssch requir
Introduce device information about vfio-ccw: VFIO_DEVICE_FLAGS_CCW.
Realize VFIO_DEVICE_GET_REGION_INFO ioctl for vfio-ccw.
Reviewed-by: Pierre Morel
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/vfio_ccw_ops.c | 78 +
include/uapi/linux/vfio.h |
Introduce ccwchain structure and helper functions that can be used to
handle a channel program issued from a virtual machine.
The following limitations apply:
1. Supports only prefetch enabled mode.
2. Supports idal(c64) ccw chaining.
3. Supports 4k idaw.
4. Supports ccw1.
5. Supports direct ccw c
Export the common I/O interfaces those are needed by an I/O
subchannel driver to actually talk to the subchannel.
Reviewed-by: Pierre Morel
Signed-off-by: Dong Jia Shi
Cc: Sebastian Ott
Cc: Peter Oberparleiter
---
drivers/s390/cio/cio.c | 10 ++
1 file changed, 10 insertions(+)
diff
We implement the basic ccw command handling infrastructure
here:
1. Translate the ccw commands.
2. Issue the translated ccw commands to the device.
3. Once we get the execution result, update the guest SCSW
with it.
Acked-by: Pierre Morel
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/vfio
Realize VFIO_DEVICE_GET_IRQ_INFO ioctl to retrieve
VFIO_CCW_IO_IRQ information.
Realize VFIO_DEVICE_SET_IRQS ioctl to set an eventfd fd for
VFIO_CCW_IO_IRQ. Once a write operation to the ccw_io_region
was performed, trigger a signal on this fd.
Reviewed-by: Pierre Morel
Signed-off-by: Dong Jia S
The patch series introduce a basic channel I/O passthrough
infrastructure based on vfio.
- Focus on supporting dasd-eckd(cu_type/dev_type = 0x3990/0x3390) as
the target device.
- Support new qemu parameters in the style of:
-machine s390-ccw-virtio(,s390-squash-mcss=on|off) \
-device vfi
To make vfio support subchannel devices, we need a css driver for
the vfio subchannels. This patch adds a basic vfio-ccw subchannel
driver for this purpose.
To enable VFIO for vfio-ccw, enable S390_CCW_IOMMU config option
and configure VFIO as required.
Acked-by: Pierre Morel
Signed-off-by: Dong
This is a placeholder for a linux-headers update.
Signed-off-by: Dong Jia Shi
---
linux-headers/linux/vfio.h | 17 +
linux-headers/linux/vfio_ccw.h | 28
2 files changed, 45 insertions(+)
create mode 100644 linux-headers/linux/vfio_ccw.h
diff --
Introduce VFIO_DEVICE_RESET ioctl for vfio-ccw to make it possible
to hot-reset the device.
We try to achieve a reset by first disabling the subchannel and
then enabling it again: this should clear all state at the subchannel.
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/vfio_ccw_ops.c | 47
The current implementation doesn't check if the subchannel is in a
proper device state when handling an event. Let's introduce
a finite state machine to manage the state/event change.
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/Makefile | 2 +-
drivers/s390/cio/vfio_ccw_drv.c
The S390 virtual css support already has a mechanism to create a
virtual subchannel and provide it to the guest. However, to
pass-through subchannels to a guest, we need to introduce a new
mechanism to create the subchannel according to the real device
information. Thus we reconstruct css_create_vi
From: Xiao Feng Ren
The S390 virtual css support already has a mechanism to build virtual
Sub-Channel Information Block and provide virtual subchannels to the
guest. However, to pass-through subchannels to a guest, we need to
introduce a new mechanism to build its schib according to the real
devi
Introduce a singlethreaded workqueue to handle the I/O interrupts.
With the work added to this queue, we store the I/O results to the
io_region of the subchannel, then signal the userspace program to
handle the results.
Signed-off-by: Dong Jia Shi
---
drivers/s390/cio/vfio_ccw_drv.c | 58 +++
Add file Documentation/s390/vfio-ccw.txt that includes details
of vfio-ccw.
Acked-by: Pierre Morel
Signed-off-by: Dong Jia Shi
---
Documentation/s390/00-INDEX | 2 +
Documentation/s390/vfio-ccw.txt | 303
2 files changed, 305 insertions(+)
create
vfio-ccw provides an MMIO region for I/O operations. We fetch its
information via ioctls here, then we can use it performing I/O
instructions and retrieving I/O results later on.
Signed-off-by: Dong Jia Shi
---
hw/vfio/ccw.c | 52
1 file chang
In order to support subchannels pass-through, we introduce a s390
subchannel device called "s390-ccw" to hold the real subchannel info.
The s390-ccw devices inherit from the abstract CcwDevice which connect
to the existing virtual-css-bus.
Signed-off-by: Dong Jia Shi
---
hw/s390x/Makefile.objs |
Add Cornelia Huck and myself as the vfio-ccw driver maintainers.
Signed-off-by: Dong Jia Shi
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c776906..01a6675 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10859,6 +10859,16 @@ W:
Although Linux does not use format-0 channel command words (CCW0)
these are a non-optional part of the platform spec, and for the sake
of platform compliance, and possibly some non-Linux guests, we have
to support CCW0.
Making the kernel execute a format 0 channel program is too much hassle
becaus
vfio-ccw resorts to the eventfd mechanism to communicate with userspace.
We fetch the irqs info via the ioctl VFIO_DEVICE_GET_IRQ_INFO,
register a event notifier to get the eventfd fd which is sent
to kernel via the ioctl VFIO_DEVICE_SET_IRQS, then we can implement
read operation once kernel sends
From: Xiao Feng Ren
We use the IOMMU_TYPE1 of VFIO to realize the subchannels
passthrough, implement a vfio based subchannels passthrough
driver called "vfio-ccw".
Support qemu parameters in the style of:
"-device vfio-ccw,sysfsdev=$mdev_file_path,devno=xx.x.'
Signed-off-by: Xiao Feng Ren
From: Xiao Feng Ren
Introduce a new callback on subchannel to handle ccw-request.
Realize the callback in vfio-ccw device. Besides, resort to
the event notifier handler to handling the ccw-request results.
1. Pread the I/O results via MMIO region.
2. Update the scsw info to guest.
3. Inject an I/
From: Xiao Feng Ren
We want to support real (i.e. not virtual) channel devices
even for guests that do not support MCSS-E (where guests may
see devices from any channel subsystem image at once). As all
virtio-ccw devices are in css 0xfe (and show up in the default
css 0 for guests not activating
hi.
I test the git qemu master have the same problem.
(gdb) bt
#0 qio_channel_socket_readv (ioc=0x7f65911b4e50, iov=0x7f64ef3fd880, niov=1,
fds=0x0, nfds=0x0, errp=0x0) at io/channel-socket.c:461
#1 0x7f658e4aa0c2 in qio_channel_read (ioc=ioc@entry=0x7f65911b4e50,
buf=buf@entry=0x7f659
From: Xiao Feng Ren
Implement a basic infrastructure of handling channel I/O instruction
interception for passed through subchannels:
1. Branch the code path of instruction interception handling by
SubChannel type.
2. For a passed-through subchannel, issue the ORB to kernel to do ccw
transl
Concurrent-sense data is currently not delivered. This patch stores
the concurrent-sense data to the subchannel if a unit check is pending
and the concurrent-sense bit is enabled. Then a TSCH can retreive the
right IRB data back to the guest.
Signed-off-by: Dong Jia Shi
---
hw/vfio/ccw.c | 7 +++
On Fri, 03/17 10:17, Fam Zheng wrote:
> BDRVReplicationState.replication_state is a name with a bit of
> duplication, plus it could be an enum like BDRVReplicationState.mode,
> which is be more readable and also more straightforward in a debuuger.
s/is be/is/
s/debuuger/debugger/
Can I blame the
On Thu, Mar 16, 2017 at 11:11:33AM +0530, Anishka0107 wrote:
> To prevent bitrot of the format string of the debug statement, files with
> conditional debug statements should ensure that printf is compiled
> always,
> and enclosed within if(0) statements and not in #ifdef.
>
> Sign
On 16/03/17 21:20, Stefano Stabellini wrote:
> On Thu, 16 Mar 2017, Juergen Gross wrote:
>> Instead of trying to guess the Xen version to use by compiling various
>> test programs first just ask the system via pkg-config. Only if it
>> can't return the version fall back to the test program scheme.
On Thu, 03/16 17:26, Ed Swierk wrote:
> On Tue, Mar 14, 2017 at 8:36 AM, Fam Zheng wrote:
> > After the AioContext lock push down, there is a race between
> > virtio_scsi_dataplane_start and those "assert(s->ctx &&
> > s->dataplane_started)", because the latter doesn't isn't wrapped in
> > aio_con
On Mar 16, 2017 23:02, "Fam Zheng" wrote:
On Thu, 03/16 17:26, Ed Swierk wrote:
> On Tue, Mar 14, 2017 at 8:36 AM, Fam Zheng wrote:
> > After the AioContext lock push down, there is a race between
> > virtio_scsi_dataplane_start and those "assert(s->ctx &&
> > s->dataplane_started)", because the
They will be used in virtio-scsi-dataplane.c as well, so move them to
header.
Signed-off-by: Fam Zheng
---
hw/scsi/virtio-scsi.c | 14 --
include/hw/virtio/virtio-scsi.h | 14 ++
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/hw/scsi/virtio-scs
v3: Don't forget the virtio_scsi_release in virtio_scsi_handle_event_vq. [Ed
Swierk]
v2: Use virtio_scsi_acquire/release. [Paolo]
Fam Zheng (2):
virtio-scsi: Make virtio_scsi_acquire/release public
virtio-scsi: Fix acquire/release in dataplane handlers
hw/scsi/virtio-scsi-dataplane.c | 20 +
After the AioContext lock push down, there is a race between
virtio_scsi_dataplane_start and those "assert(s->ctx &&
s->dataplane_started)", because the latter doesn't isn't wrapped in
aio_context_acquire.
Reproducer is simply booting a Fedora guest with an empty
virtio-scsi-dataplane controller:
On 03/17/2017 05:28 AM, Andrew Morton wrote:
On Thu, 16 Mar 2017 15:08:46 +0800 Wei Wang wrote:
From: Liang Li
This patch adds a function to provides a snapshot of the present system
unused pages. An important usage of this function is to provide the
unsused pages to the Live migration threa
201 - 285 of 285 matches
Mail list logo
