For now, we use inotify watches to track only a small number of
events, namely, add, delete and modify. Note that for delete, the kernel
already deactivates the watch for us and we just need to
take care of modifying our internal state.
inotify is a linux only mechanism.
Suggested-by: Gerd Hoffma
On Thu, 2015-11-19 at 15:29 +1100, David Gibson wrote:
> At present the code handling IBM's Enhanced Error Handling (EEH) interface
> on VFIO devices operates by bypassing the usual VFIO logic with
> vfio_container_ioctl(). That's a poorly designed interface with unclear
> semantics about exactly
ab59e3e introduced a fix for `make install` on w32 that involved
filtering out qemu-ga from $TOOLS install recipe so that we could
append $(EXESUF) to it before attempting to install the binary
via install-prog function.
install-prog takes a list of binaries to install to a particular
directory. I
My qemu build has been failing since this checkin by Michael Roth:
http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg03991.html
which changed the top-level Makefile. Is anyone else seeing this?
I am building a qemu for MIPS on an x86 linux box with:
configure --prefix=/scratch
Quoting Michael Roth (2015-11-23 12:35:57)
> Quoting Steve Ellcey (2015-11-23 12:06:57)
> > My qemu build has been failing since this checkin by Michael Roth:
> >
> >
> > http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg03991.html
> >
> > which changed the top-level Makefile.
On 11/20/2015 01:18 PM, Marc-André Lureau wrote:
> Hi
>
> - Original Message -
Hash ivshmem been used in anger? If yes, how?
>>
>> Still the question to answer.
>
> I don't expect users to read this ML everyday (anybody actually). Personally,
> I have no clue how widespread ivshmem
On Mon, Nov 23, 2015 at 05:13:37PM +0100, Thomas Huth wrote:
> The "pseries" alias is currently set twice, one time for the
> pseries-2.4 machine and one time for the "pseries-2.5" machine.
> To avoid confusion with the alias, let's remove the one from
> the older machine class. And while we're at
On Fri, 2015-11-20 at 18:45 +1100, David Gibson wrote:
>
> So, I'm not 100% following the logic below, but it looks like the
> existing code used SPR_NOACCESS to mark things which generated a
> privilege exception compared to NULL for things which generated an
> invalid instruction exception. Usi
On 11/24/2015 12:30 AM, Eric Blake wrote:
> On 11/22/2015 11:23 PM, Wen Congyang wrote:
>> The new QMP command name is x-blockdev-change. It justs for adding/removing
>
> s/It justs/It's just/
>
>> quorum's child now, and don't support all kinds of children, all kinds of
>
> s/don't/doesn't/
>
On Fri, 2015-11-20 at 18:45 +1100, David Gibson wrote:
> snip]
> > /* tlbiel */
> > static void gen_tlbiel(DisasContext *ctx)
> > {
> > #if defined(CONFIG_USER_ONLY)
> > - gen_inval_exception(ctx, POWERPC_EXCP_PRIV_OPC);
> > + GEN_PRIV;
> > #else
> > - if (unlikely(ctx->pr || !ctx->hv
On Fri, 2015-11-20 at 18:48 +1100, David Gibson wrote:
>
> > @@ -380,9 +380,11 @@ typedef struct opcode_t {
> > #if defined(CONFIG_USER_ONLY)
> > #define CHK_HV GEN_PRIV
> > #define CHK_SV GEN_PRIV
> > +#define CHK_HVDR GEN_PRIV
>
> I'm guessing this is supposed to be CHK_HVRM as below.
Indee
On Fri, 2015-11-20 at 18:53 +1100, David Gibson wrote:
> On Wed, Nov 11, 2015 at 11:27:37AM +1100, Benjamin Herrenschmidt
> wrote:
> > There's no point inlining this, if you hit the exception case you
> > exit anyway,
>
> That doesn't quite seem relevant - IIUC this is affecting inlining in
> the
On 11/23/2015 11:59 PM, Kevin Wolf wrote:
> Some drivers have nested options (e.g. blkdebug rule arrays), which
> don't belong to a child node and shouldn't be removed. Don't remove all
> options with "." in their name, but check for the complete prefixes of
> actually existing child nodes.
>
> Si
On Mon, Nov 23, 2015 at 08:41:20AM +0800, Fam Zheng wrote:
> "werror=report" would free the req in virtio_blk_handle_rw_error, we
> mustn't write to it in that case.
>
> Reported-by: Paolo Bonzini
> Signed-off-by: Fam Zheng
> ---
> hw/block/virtio-blk.c | 7 +++
> 1 file changed, 3 insertio
On Mon, Nov 23, 2015 at 12:54:56PM +0200, Michael S. Tsirkin wrote:
> It seems that we currently have some duplication between
> started and enabled states.
>
> The actual reason is that enable is not documented correctly:
> what it does is connecting ring to the backend.
>
> This is important fo
On Fri, 2015-11-20 at 19:21 +1100, David Gibson wrote:
> On Wed, Nov 11, 2015 at 11:27:39AM +1100, Benjamin Herrenschmidt
> wrote:
> > No devices yet, not even an interrupt controller, just to get
> > started.
> >
> > Signed-off-by: Benjamin Herrenschmidt
> > ---
> > default-configs/ppc64-softmm
Hi, all,
CC'ing all the reviewers.
Sorry to not respond one by one, just trying to avoid spliting into
several emails and people spend extra time reading them, especially
if this patch is to be dropped.
Please check bottom reply.
On 11/24/2015 01:57 AM, Andrew Jones wrote:
> On Mon, Nov 23, 201
On Mon, 11/23 16:34, John Snow wrote:
> Hmm, what's the idea, here?
>
> This patch does a lot more than just hide hbitmap details from callers
> of block_dirty_bitmap functions.
>
> So we're changing the backing hbitmap to always be one where g=0 and the
> number of physical bits directly is (now
On Tue, Nov 24, 2015 at 11:51:44AM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2015-11-20 at 18:45 +1100, David Gibson wrote:
> > snip]
> > > /* tlbiel */
> > > static void gen_tlbiel(DisasContext *ctx)
> > > {
> > > #if defined(CONFIG_USER_ONLY)
> > > - gen_inval_exception(ctx, POWERPC_E
On Tue, Nov 24, 2015 at 11:44:36AM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2015-11-20 at 18:45 +1100, David Gibson wrote:
> >
> > So, I'm not 100% following the logic below, but it looks like the
> > existing code used SPR_NOACCESS to mark things which generated a
> > privilege exception co
Hi,
> -Original Message-
> From: Cornelia Huck [mailto:cornelia.h...@de.ibm.com]
> Sent: Monday, November 23, 2015 11:14 PM
> Subject: Re: [virtio-dev] [RFC v1] virtio-crypto specification
>
> On Fri, 20 Nov 2015 03:27:51 +
> "Gonglei (Arei)" wrote:
>
> > Hi guys,
> >
> > After init
On Mon, 11/23 09:10, Eric Blake wrote:
> On 11/23/2015 03:07 AM, Peter Xu wrote:
> > This patch only add the interfaces, but not implementing them.
> >
> > Signed-off-by: Peter Xu
> > ---
> > dump.c | 3 ++-
> > hmp-commands.hx | 5 +++--
> > hmp.c| 3 ++-
> > qapi-schema.
On 2015/11/18 18:51, Juan Quintela wrote:
zhanghailiang wrote:
For migration destination, sometimes we need to know its state,
and it is also useful for tracing migration incoming process.
Here we add a new member 'state' for MigrationIncomingState,
and also use migrate_set_state() to modify i
On Tue, 11/24 09:57, Peter Xu wrote:
> On 11/24/2015 01:57 AM, Andrew Jones wrote:
> > On Mon, Nov 23, 2015 at 05:22:29PM +0100, Laszlo Ersek wrote:
> >> On 11/23/15 11:07, Peter Xu wrote:
> >>> Currently, dump-guest-memory supports synchronous operation only. This
> >>> patch
> >>> sets are addin
On Nov 23, 2015, at 11:06 AM, Peter Maydell wrote:
> On 22 November 2015 at 01:43, Programmingkid
> wrote:
>> When QEMU is brought to the foreground, the click event that activates QEMU
>> should not go to the guest. Accidents happen when they do go to the guest
>> without giving the user a cha
On Mon, Nov 23, 2015 at 6:51 PM, KONRAD Frederic
wrote:
>
>
> Le 20/11/2015 11:06, Alistair Francis a écrit :
>>
>> On Fri, Oct 16, 2015 at 7:11 PM, wrote:
>>>
>>> From: KONRAD Frederic
>>>
>>> This is the implementation of the DisplayPort.
>>> It has an aux-bus to access dpcd and edid.
>>>
>>>
On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:
> On 22/11/15 17:39, Programmingkid wrote:
>
> Hi Alfonso,
>
> Has there been any progress at all as to which extensions may be causing
> the crashes?
Remove these extensions from the Extensions folder and Mac OS 9
Following changes are made to the TSC rate setting code in
kvm_arch_init_vcpu():
* The code is moved to a new function kvm_arch_set_tsc_khz().
* If kvm_arch_set_tsc_khz() fails, i.e. following two conditions are
both satisfied:
* KVM does not support the TSC scaling or it fails to set vcpu'
This patch enables migrating vcpu's TSC rate. If KVM on the destination
machine supports TSC scaling, guest programs will observe a consistent
TSC rate across the migration.
If TSC scaling is not supported on the destination machine, the
migration will not be aborted and QEMU on the destination wi
This patchset enables QEMU to save/restore vcpu's TSC rate during the
migration on machine types pc-*-2.5 or newer.
On the source machine:
* If the vcpu's TSC rate is specified by the cpu option 'tsc-freq',
then this user-specified TSC rate will be migrated.
* Otherwise, the TSC rate returned
If no user-specified TSC rate is present, we will try to set
env->tsc_khz to the value returned by KVM_GET_TSC_KHZ. This patch does
not change the current functionality of QEMU and just prepares for later
patches to enable migrating vcpu's TSC rate.
Signed-off-by: Haozhong Zhang
---
target-i386/
On Mon, Nov 23, 2015 at 6:53 PM, KONRAD Frederic
wrote:
>
>
> Le 20/11/2015 13:21, Alistair Francis a écrit :
>>
>> On Fri, Oct 16, 2015 at 7:11 PM, wrote:
>>>
>>> From: KONRAD Frederic
>>>
>>> This adds the DP and the DPDMA to the Zynq MP platform.
>>>
>>> Signed-off-by: KONRAD Frederic
>>> R
On Mon, Nov 23, 2015 at 05:31:33PM +0100, Juan Quintela wrote:
> Wen Congyang wrote:
> > If we set migration speed in a very large value, block-migration will try
> > to read
> > all data to the memory. Because
> > (block_mig_state.submitted + block_mig_state.read_done) * BLOCK_SIZE
> > will
Hello,
The 2.5 release is close - and I'm collecting a list of notable
changes and features once more. The video made for the 2.4 release
[1] was popular, and I'm volunteering to make one for 2.5 as well. In
addition, we need more feature pages, and there's a template at [2]
that you can use to
The Xilinx EP108 supports three memory regions:
- A 2GB region starting at 0
- A 32GB region starting at 32GB
- A 256GB region starting at 768GB
This patch adds support for the middle memory region, which is
automatically created based on the size specified by the QEMU memory
command line argum
On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:
> On 22/11/15 17:39, Programmingkid wrote:
>
> Hi Alfonso,
>
> Has there been any progress at all as to which extensions may be causing
> the crashes?
Remove these extensions from the Extensions folder and Mac OS 9
I stumbled upon this when looking at external bitmap formats.
Current "qemu-img map" command only displays filename if the data is allocated
in bs (bs->file) itself, or in the backing chain. Otherwise, it displays an
unfriendly error message:
$ qemu-img create -f vmdk -o subformat=monolithicF
The added parameter can be used to return the BDS pointer which the
valid offset is refering to. It's value should be ignored unless
BDRV_BLOCK_OFFSET_VALID in ret is set.
Until block drivers fill in the right value, let's clear it explicitly
right before calling .bdrv_get_block_status.
Signed-of
Signed-off-by: Fam Zheng
---
block/qcow.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/qcow.c b/block/qcow.c
index 558f443..b59383f 100644
--- a/block/qcow.c
+++ b/block/qcow.c
@@ -509,6 +509,7 @@ static int64_t coroutine_fn
qcow_co_get_block_status(BlockDriverState *bs,
re
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/059 | 10 ++
tests/qemu-iotests/059.out | 38 ++
2 files changed, 48 insertions(+)
diff --git a/tests/qemu-iotests/059 b/tests/qemu-iotests/059
index 0ded0c3..261d8b0 100755
--- a/tests/qemu-iotests/0
Signed-off-by: Fam Zheng
---
block/qcow2.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/qcow2.c b/block/qcow2.c
index 836888c..7634c42 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -1302,6 +1302,7 @@ static int64_t coroutine_fn
qcow2_co_get_block_status(BlockDriverState *bs,
Signed-off-by: Fam Zheng
---
block/qed.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/block/qed.c b/block/qed.c
index a6bbd8b..03af9c1 100644
--- a/block/qed.c
+++ b/block/qed.c
@@ -692,6 +692,7 @@ typedef struct {
uint64_t pos;
int64_t status;
int *pnum;
+BlockDriver
Signed-off-by: Fam Zheng
---
block/raw-posix.c | 1 +
block/raw_bsd.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/block/raw-posix.c b/block/raw-posix.c
index 2cd7d68..9988aa4 100644
--- a/block/raw-posix.c
+++ b/block/raw-posix.c
@@ -1873,6 +1873,7 @@ static int64_t coroutine_fn
raw_
Signed-off-by: Fam Zheng
---
block/parallels.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/parallels.c b/block/parallels.c
index 04f0e87..d1406b1 100644
--- a/block/parallels.c
+++ b/block/parallels.c
@@ -273,6 +273,7 @@ static int64_t coroutine_fn
parallels_co_get_block_status(Blo
Signed-off-by: Fam Zheng
---
block/sheepdog.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/block/sheepdog.c b/block/sheepdog.c
index 0f6789e..d5e7ff8 100644
--- a/block/sheepdog.c
+++ b/block/sheepdog.c
@@ -2740,6 +2740,9 @@ sd_co_get_block_status(BlockDriverState *bs, int64_t
sector_n
Signed-off-by: Fam Zheng
---
block/iscsi.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/block/iscsi.c b/block/iscsi.c
index 2d1e230..8c7f1b3 100644
--- a/block/iscsi.c
+++ b/block/iscsi.c
@@ -625,6 +625,9 @@ out:
if (iTask.task != NULL) {
scsi_free_scsi_task(iTask.task);
Signed-off-by: Fam Zheng
---
block/vmdk.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/block/vmdk.c b/block/vmdk.c
index f5a56fd..b60a5af 100644
--- a/block/vmdk.c
+++ b/block/vmdk.c
@@ -1265,6 +1265,7 @@ static int64_t coroutine_fn
vmdk_co_get_block_status(Blo
Signed-off-by: Fam Zheng
---
block/vpc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/block/vpc.c b/block/vpc.c
index 912f5d0..412ff41 100644
--- a/block/vpc.c
+++ b/block/vpc.c
@@ -588,6 +588,7 @@ static int64_t coroutine_fn
vpc_co_get_block_status(BlockDriverState *bs,
if (be32
Signed-off-by: Fam Zheng
---
block/vdi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/vdi.c b/block/vdi.c
index 2199fd3..6b1a57b 100644
--- a/block/vdi.c
+++ b/block/vdi.c
@@ -550,6 +550,7 @@ static int64_t coroutine_fn
vdi_co_get_block_status(BlockDriverState *bs,
offset = s->
The new "file" output parameter of bdrv_get_block_status tells which
file the valid offset is referring to, we can use the information and
output the filename.
The iotest 122 reference output is updated accordingly.
Signed-off-by: Fam Zheng
---
qemu-img.c | 12
test
On Mon, Nov 23, 2015 at 7:28 PM, Programmingkid
wrote:
>
> On Nov 23, 2015, at 4:00 PM, Mark Cave-Ayland wrote:
>
> > On 22/11/15 17:39, Programmingkid wrote:
> >
> > Hi Alfonso,
> >
> > Has there been any progress at all as to which extensions may be
> causing
> > the crashes?
>
Switch json output generation from hand-written to QDict encoder, so
that the coming str field will be properly escaped.
Iotest 122 output is updated accordingly.
Signed-off-by: Fam Zheng
---
qemu-img.c | 30 +++
tests/qemu-iotests/122.out | 96 ++
On 11/23/2015 10:21 PM, Fam Zheng wrote:
> The added parameter can be used to return the BDS pointer which the
> valid offset is refering to. It's value should be ignored unless
s/refering/referring/
> BDRV_BLOCK_OFFSET_VALID in ret is set.
>
> Until block drivers fill in the right value, let's
v2: bitmap_set -> set_bit. [Congyang, Paolo, John]
Add John Snow's rev-by with that change.
This makes a cleaner base for more dirty bitmap work. "granularity" appearing
with different representations have always been mind twisting, remove it from
HBitmap to make the interface and implementati
HBitmap is an implementation detail of block dirty bitmap that should be hidden
from users. Introduce a BdrvDirtyBitmapIter to encapsulate the underlying
HBitmapIter.
A small difference in the interface is, before, an HBitmapIter is initialized
in place, now the new BdrvDirtyBitmapIter must be dyn
"s->bitmap" tracks done sectors, we only check bit states without using any
iterator which HBitmap is good for. Switch to "Bitmap" which is simpler and
more memory efficient.
Meanwhile, rename it to done_bitmap, to reflect the intention.
Signed-off-by: Fam Zheng
Reviewed-by: John Snow
---
bloc
Sometimes confused with the granularity with coarse levels in HBitmap, the
granularity in the hbitmap_alloc is not an essential concept of a bitmap. Now
that all callers except the test code use zero, it's possible to drop the
parameter to make the interface cleaner and more intuitive.
Test code
On 11/23/2015 04:06 PM, Michael S. Tsirkin wrote:
> On Mon, Nov 23, 2015 at 03:41:11PM +0800, Jason Wang wrote:
>> Currently, all virtio devices bypass IOMMU completely. This is because
>> address_space_memory is assumed and used during DMA emulation. This
>> patch converts the virtio core API to
(to: Kevin and cc: qemu-block)
On Fri, Nov 13, 2015 at 02:17:28PM +0100, Ricard Wanderlöf wrote:
>
> For the "main area on file, oob in memory" case, fix the shifts so that
> we erase the correct number of pages.
>
> Signed-off-by: Ricard Wanderlöf
> ---
> hw/block/nand.c |2 +-
> 1 file c
On 11/23/2015 05:36 PM, Cornelia Huck wrote:
> On Mon, 23 Nov 2015 15:41:11 +0800
> Jason Wang wrote:
>
>> Currently, all virtio devices bypass IOMMU completely. This is because
>> address_space_memory is assumed and used during DMA emulation. This
>> patch converts the virtio core API to use DM
On 11/23/2015 10:22 PM, Fam Zheng wrote:
> Switch json output generation from hand-written to QDict encoder, so
> that the coming str field will be properly escaped.
>
> Iotest 122 output is updated accordingly.
>
> Signed-off-by: Fam Zheng
> ---
> qemu-img.c | 30 +++---
On Mon, 11/23 22:30, Eric Blake wrote:
> On 11/23/2015 10:21 PM, Fam Zheng wrote:
> > The added parameter can be used to return the BDS pointer which the
> > valid offset is refering to. It's value should be ignored unless
>
> s/refering/referring/
>
> > BDRV_BLOCK_OFFSET_VALID in ret is set.
> >
On Mon, Nov 23, 2015 at 01:39:04PM +0100, Kevin Wolf wrote:
> I tried to run "make check" on my mingw build and got two failures. Both of
> them are bugs in the test suite rather than qemu proper. They are easy enough
> to fix, so here are the fixes.
>
> Kevin Wolf (2):
> tests/Makefile: Add mor
On Mon, 11/23 22:42, Eric Blake wrote:
> On 11/23/2015 10:22 PM, Fam Zheng wrote:
> > +++ b/tests/qemu-iotests/122.out
> > @@ -49,12 +49,13 @@ read 65536/65536 bytes at offset 4194304
> > 64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > read 65536/65536 bytes at offset 8388608
> > 64
On Wed, Nov 11, 2015 at 11:27:45AM +1100, Benjamin Herrenschmidt wrote:
> The "ICP" is a different object than the "XICS". For historical reasons,
> we have a number of places where we name a variable "icp" while it contains
> a XICSState pointer. There *is* an ICPState structure too so this makes
On Wed, Nov 11, 2015 at 11:27:44AM +1100, Benjamin Herrenschmidt wrote:
> Signed-off-by: Benjamin Herrenschmidt
Reviewed-by: David Gibson
In fact, this is a sufficiently good clean up that I think I'll merge
it shortly, regardless of what happens with the rest of the pnv series.
> ---
> hw/in
On Wed, Nov 11, 2015 at 11:27:40AM +1100, Benjamin Herrenschmidt wrote:
> XSCOM is an interface to a sideband bus provided by the POWER8 chip
> pervasive unit, which gives access to a number of facilities in the
> chip that are needed by the OPAL firmware and to a lesser extent,
> Linux. This is am
On Wed, Nov 11, 2015 at 11:27:41AM +1100, Benjamin Herrenschmidt wrote:
> The common class doesn't change, the KVM one is SPAPR specific, this
> is a preliminary change to make it easier to support "native" XICS.
>
> Signed-off-by: Benjamin Herrenschmidt
So changing the variable names is fine, b
On Wed, Nov 11, 2015 at 11:27:42AM +1100, Benjamin Herrenschmidt wrote:
> Leave the core ICP/ICS logic in xics.c and move the top level
> class wrapper, hypercall and RTAS handlers to xics_spapr.c
>
> Signed-off-by: Benjamin Herrenschmidt
Concept looks fine.
> ---
> default-configs/ppc64-softm
On Tue, Nov 24, 2015 at 12:45:48PM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2015-11-20 at 19:21 +1100, David Gibson wrote:
> > On Wed, Nov 11, 2015 at 11:27:39AM +1100, Benjamin Herrenschmidt
> > wrote:
> > > No devices yet, not even an interrupt controller, just to get
> > > started.
> > >
On Sat, 2015-11-21 at 23:45 -0800, Ming Lin wrote:
> On Sat, 2015-11-21 at 13:56 +0100, Paolo Bonzini wrote:
> >
> > On 21/11/2015 00:05, Ming Lin wrote:
> > > [1.752129] Freeing unused kernel memory: 420K (880001b97000 -
> > > 880001c0)
> > > [1.986573] clocksource: tsc: mask
"Daniel P. Berrange" writes:
> On Mon, Nov 23, 2015 at 07:41:24PM +0100, Lluís Vilanova wrote:
>> Gives some general guidelines for reporting errors in QEMU.
>>
>> Signed-off-by: Lluís Vilanova
>> ---
>> HACKING | 31 +++
>> 1 file changed, 31 insertions(+)
>>
>>
On Mo, 2015-11-23 at 09:18 -0500, Gabriel L. Somlo wrote:
> Ping ?
>
> I can send out v6 and fix the commit blurb typo in patch 6/6 pointed
> out by Laszlo (unless the series is already winding its way toward
> eventually being applied).
>
> Please advise.
We are in 2.5 hard-freeze, so this is f
On Mon, 2015-11-23 at 15:14 +0100, Paolo Bonzini wrote:
>
> On 23/11/2015 09:17, Ming Lin wrote:
> > On Sat, 2015-11-21 at 14:11 +0100, Paolo Bonzini wrote:
> >>
> >> On 20/11/2015 01:20, Ming Lin wrote:
> >>> One improvment could be to use google's NVMe vendor extension that
> >>> I send in anoth
On Mo, 2015-11-23 at 16:37 -0500, Bandan Das wrote:
> This series adds support for mtp events that are piggybacked on
> top of the Linux provided inotify mechanism. It performs well with some
> light unit testing in a linux guest. The mtp share is still read only,
> but now the guest will notice up
"Daniel P. Berrange" writes:
> On Mon, Nov 23, 2015 at 09:05:30PM +0100, Lluís Vilanova wrote:
>> Daniel P Berrange writes:
>> [...]
>> > I don't think this "Errors in user inputs" vs "Other errors" distinction
>> > really makes sense. Whether an error raised in a piece of code is related
>> > to
201 - 276 of 276 matches
Mail list logo
