On 11/23/15 19:09, Paolo Bonzini wrote:
>
>
> On 23/11/2015 18:59, Laszlo Ersek wrote:
The only interesting thing is that parse_keyword always eats
a TOKEN_KEYWORD, even if it is invalid, so it must come last in
parse_value (otherwise, NULL is returned, parse_literal is invoked
On 11/19/2015 08:35 AM, Michael S. Tsirkin wrote:
> ich calls acpi_gpe_init with length ICH9_PMIO_GPE0_LEN so
> ICH9_PMIO_GPE0_LEN/2 bytes are allocated, but then the full
> ICH9_PMIO_GPE0_LEN bytes are migrated.
>
> As a quick work-around, allocate twice the memory.
> We'll probably want to
On 11/23/15 20:31, Gabriel L. Somlo wrote:
> Couple of items:
>
> 1. Ping ? :)
>
> 2. Thank you markmb for your R-b !
>
> 3. If anyone's had a chance to look over the corresponding guest-side
>kernel sysfs driver which utilizes this, you will have noticed I'm
>automatically initializing
Couple of items:
1. Ping ? :)
2. Thank you markmb for your R-b !
3. If anyone's had a chance to look over the corresponding guest-side
kernel sysfs driver which utilizes this, you will have noticed I'm
automatically initializing the driver based on DeviceTree or ACPI
on ARM and x86,
On Mon, Nov 23, 2015 at 05:43:14PM +0100, Borislav Petkov wrote:
> On Mon, Nov 23, 2015 at 01:11:27PM -0200, Eduardo Habkost wrote:
> > On Mon, Nov 23, 2015 at 11:22:37AM -0200, Eduardo Habkost wrote:
> > [...]
> > > In the case of this code, it looks like it's already broken
> > > because the
Markus Armbruster writes:
> Lluís Vilanova writes:
>> When adding a new QAPI command, should I also add a corresponding entry in
>> "qmp-commands.hx"?
> Yes.
> Towards the end of the very long QAPI patch queue are patches to get rid
> of qmp-commands.hx. We'll get there,
On 11/23/2015 07:46 AM, Markus Armbruster wrote:
>>> If it's not broken, please explain to me how the guest should find out
>>> whether its ivshmem device sports a doorbell.
>>
>> If you have received ID, you should be good to use the doorbell.
>
> That's not a complete answer, so let me try a
On 23/11/2015 18:59, Laszlo Ersek wrote:
>> > The only interesting thing is that parse_keyword always eats
>> > a TOKEN_KEYWORD, even if it is invalid, so it must come last in
>> > parse_value (otherwise, NULL is returned, parse_literal is invoked
>> > and it tries to peek beyond end of input).
On Mon, Nov 23, 2015 at 07:01:33PM +0100, Marc-André Lureau wrote:
> On Mon, Nov 23, 2015 at 6:40 PM, Paolo Bonzini wrote:
> > Before: object-initial, chardev, qtest, object-late (not in the patch)
> >
> > After: chardev, qtest, object-initial, object-late (not in the patch)
Adds support for reporting non-terminating errors (dubbed warnings), and briefly
documents what routines should developers generally use to keep error reporting
consistent.
Changes in v2
=
* Split in two patches.
* Explicitly add a warning error object.
Signed-off-by: Lluís
When adding a new QAPI command, should I also add a corresponding entry in
"qmp-commands.hx"?
Thanks,
Lluis
--
"And it's much the same thing with knowledge, for whenever you learn
something new, the whole world becomes that much richer."
-- The Princess of Pure Reason, as told by Norton
Markus Armbruster writes:
> Marc-André Lureau writes:
[...]
>>> * shm appears to be the same as memdev, just less flexible. Why does it
>>> exist?
>>
>> It was there before.
>
> Not only is memdev more flexible, it also provides the clean split
>
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. Is anyone else seeing this?
>
> I am building a qemu for
Adds a special error object that transforms error messages into
immediately reported warnings.
Signed-off-by: Lluís Vilanova
---
include/qapi/error.h | 20
util/error.c | 37 +++--
2 files changed, 47
On 23.11.2015 19:49, Peter Maydell wrote:
> Ping? I forgot to mark this for-2.5, and given how long the bug's
> been hanging around there's not much urgency to fixing it, but
> we might as well put the fix into 2.5 if it gets reviewed.
>
Hi, Peter. I'm going to review this carefully in a few days
Gives some general guidelines for reporting errors in QEMU.
Signed-off-by: Lluís Vilanova
---
HACKING | 31 +++
1 file changed, 31 insertions(+)
diff --git a/HACKING b/HACKING
index 12fbc8a..e59bc34 100644
--- a/HACKING
+++ b/HACKING
@@ -157,3
On 11/23/2015 10:59 AM, Laszlo Ersek wrote:
> On 11/23/15 18:44, Paolo Bonzini wrote:
>> JSON is LL(1) and our parser indeed needs only 1 token lookahead.
>> Saving the parser context is mostly unnecessary; we can replace it
>> with peeking at the next token, or remove it altogether when the
>>
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 user input or not is almost impossible to determine in practice. So as
> a rule to follow it is not practical.
Hi Gabriel,
[auto build test WARNING on v4.4-rc2]
[also build test WARNING on next-20151123]
[cannot apply to robh/for-next]
url:
https://github.com/0day-ci/linux/commits/Gabriel-L-Somlo/SysFS-driver-for-QEMU-fw_cfg-device/20151124-000402
config: arm-allyesconfig (attached as .config
Hi
- Original Message -
> On 11/23/2015 07:46 AM, Markus Armbruster wrote:
>
> >>> If it's not broken, please explain to me how the guest should find out
> >>> whether its ivshmem device sports a doorbell.
> >>
> >> If you have received ID, you should be good to use the doorbell.
> >
>
On Mon, Nov 23, 2015 at 08:46:33PM +0100, Laszlo Ersek wrote:
> On 11/23/15 20:31, Gabriel L. Somlo wrote:
> > Couple of items:
> >
> > 1. Ping ? :)
> >
> > 2. Thank you markmb for your R-b !
> >
> > 3. If anyone's had a chance to look over the corresponding guest-side
> >kernel sysfs
On 11/23/15 21:05, Eric Blake wrote:
> On 11/23/2015 10:59 AM, Laszlo Ersek wrote:
>> On 11/23/15 18:44, Paolo Bonzini wrote:
>>> JSON is LL(1) and our parser indeed needs only 1 token lookahead.
>>> Saving the parser context is mostly unnecessary; we can replace it
>>> with peeking at the next
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 user input or not is almost
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 use DMA API. This idea is
>
> - introducing a new
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 another thread, aslo here:
> > https://git.kernel.org/cgit/linux/kernel/git/mlin/linux.git/log/?h=nvme-google-ext
>
On 11/20/2015 05:59 PM, Fam Zheng wrote:
> "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.
>
>
On Mon, 11/23 08:33, Markus Armbruster wrote:
> Fam Zheng writes:
>
> > Otherwise, a window flashes on my desktop (built with SDL). Add this as
> > other cases have it.
> >
> > Signed-off-by: Fam Zheng
> >
> > ---
> > v2: Fix 119 too. [Max]
> > ---
> >
On 11/23/2015 05:19 PM, Fam Zheng wrote:
> On Mon, 11/23 17:01, Wen Congyang wrote:
>> On 11/20/2015 05:59 PM, Fam Zheng wrote:
>>> "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
On Mon, 11/23 17:24, Wen Congyang wrote:
> On 11/23/2015 05:19 PM, Fam Zheng wrote:
> > On Mon, 11/23 17:01, Wen Congyang wrote:
> >> On 11/20/2015 05:59 PM, Fam Zheng wrote:
> >>> "s->bitmap" tracks done sectors, we only check bit states without using
> >>> any
> >>> iterator which HBitmap is
On Tue, Nov 17, 2015 at 08:02:58PM +0300, Denis V. Lunev wrote:
> From: Vladimir Sementsov-Ogievskiy
>
> This patch marks part of the BAT dirty properly. There is a possibility that
> multy-block allocation could have one block allocated on one BAT page and
> next block
To return from a signal, setup_frame() puts an instruction to
be executed in the stack. This sequence calls the syscall sigreturn().
The address of the instruction must be set in the PR register
to be executed.
This patch fixes this: the current code sets the register to the address
of the
On 11/23/2015 11:38 AM, Laurent Vivier wrote:
> Signed-off-by: Laurent Vivier
Tested-by: John Paul Adrian Glaubitz
This patch fixes crashes of qemu-sh4* on amd64 for me [1].
I also haven't seen any regressions ever since.
Cheers,
Adrian
> [1]
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 for MQ, because a Linux guest expects TX
packets to be completed even if it
On 11/20/2015 01:42 PM, Wen wrote:
> To Jason Wang:
>
> I think this patch should be for qemu-2.5
>
> Thanks
> Wen Congyang
Hi:
I thought it was for vhost tree.
Michael:
Do you want to take this patch?
>
> On 11/11/2015 02:53 PM, Wen Congyang wrote:
>> Signed-off-by: Wen Congyang
On Mon, Nov 23, 2015 at 09:35:31AM +0100, Markus Armbruster wrote:
> qmp_query_memdev() has two error paths:
>
> * When object_get_objects_root() returns null. It never does, so
> simply drop the useless error handling.
>
> * When query_memdev() fails. It leaks err then. But any failure
>
On Mon, 11/23 17:01, Wen Congyang wrote:
> On 11/20/2015 05:59 PM, Fam Zheng wrote:
> > "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
Am 20.11.2015 um 13:53 hat Markus Armbruster geschrieben:
> Spotted by Coverity.
>
> Signed-off-by: Markus Armbruster
Reviewed-by: Kevin Wolf
On 23/11/2015 11:09, Paolo Bonzini wrote:
> On 23/11/2015 07:41, Pavel Fedin wrote:
>> Hello! No news for a long time, we are at RC stage. Could we get this in?
>
> Yes, queued for -rc2.
... doh, Eduardo applied it to the NUMA tree already. I missed that
backends/hostmem* is under NUMA and
Marc-André Lureau writes:
> 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
From: John Clarke
A simple typo in the variable to use when comparing vs the highwater mark.
Reports are that qemu can in fact segfault occasionally due to this mistake.
Signed-off-by: John Clarke
Signed-off-by: Richard Henderson
---
at:
git://github.com/rth7680/qemu.git tags/pull-tcg-20151123
for you to fetch changes up to 644da9b39e477caa80bab69d2847dfcb468f0d33:
tcg: Fix highwater check (2015-11-23 13:16:05 +0100)
Last minute fix
(I forgot to submit a pull request for this earlier, sorry.)
The following changes since commit 541abd10a01da56c5f16582cd32d67114ec22a5c:
Update version for v2.5.0-rc1 release (2015-11-20 17:43:46 +)
are available in the git repository at:
git://github.com/ehabkost/qemu.git
Ping? Any thoughts on this approach?
-rc2 is too late for this kind of change, maybe?
On Thu, Nov 12, 2015 at 03:29:53PM -0200, Eduardo Habkost wrote:
> This changes the qemu_hw_version() default to "2.5+" so we don't
> make every machine class broken by default unless they set
> hw_version.
>
From: Pavel Fedin
Currently hostmem backend fails if CONFIG_NUMA is enabled in QEMU
(the default) but NUMA is not supported by the kernel. This makes
it impossible to use ivshmem in such configurations.
This patch fixes the problem by ignoring ENOSYS error if policy is set
Am 23.11.2015 um 13:45 schrieb Richard Henderson:
> From: John Clarke
>
> A simple typo in the variable to use when comparing vs the highwater mark.
> Reports are that qemu can in fact segfault occasionally due to this mistake.
>
> Signed-off-by: John Clarke
On Fri, Nov 20, 2015 at 18:24:29 +0530, Bharata B Rao wrote:
> This patchset adds CPU hotplug support for sPAPR PowerPC guests using
> device_add and device_del commands
>
> (qemu) device_add POWER8-powerpc64-cpu,id=cpu0
Is there a reason why this uses 'device_add' rather than the 'cpu_add'
On Fri, Nov 20, 2015 at 03:15:27PM -0700, Eric Blake wrote:
> On 11/20/2015 11:04 AM, Daniel P. Berrange wrote:
> > Add a 'keyid' parameter that refers to the ID of a
> > QCryptoSecret instance that provides the encryption key.
> >
> > $QEMU \
> > -object
On Mon, Nov 23, 2015 at 10:53:39AM -0200, Eduardo Habkost wrote:
>
> Ping? Any thoughts on this approach?
>
> -rc2 is too late for this kind of change, maybe?
>
I queued this up for 2.5, will merge later this week
unless anyone objects.
> On Thu, Nov 12, 2015 at 03:29:53PM -0200, Eduardo
On 11/23/2015 12:54 PM, Peter Krempa wrote:
> On Fri, Nov 20, 2015 at 18:24:29 +0530, Bharata B Rao wrote:
>> This patchset adds CPU hotplug support for sPAPR PowerPC guests using
>> device_add and device_del commands
>>
>> (qemu) device_add POWER8-powerpc64-cpu,id=cpu0
>
> Is there a reason why
"Michael S. Tsirkin" writes:
> On Mon, Nov 23, 2015 at 09:35:31AM +0100, Markus Armbruster wrote:
>> qmp_query_memdev() has two error paths:
>>
>> * When object_get_objects_root() returns null. It never does, so
>> simply drop the useless error handling.
>>
>> * When
On Fri, Nov 20, 2015 at 02:32:51PM +, Peter Maydell wrote:
> In an LPAE format descriptor in ARMv8 the address field extends
> up to bit 47, not just bit 39. Correct the masking so we don't
> give incorrect results if the output address size is greater
> than 40 bits, as it can be for AArch64.
Hi
- Original Message -
>
> >> qemu-doc documents role only with chardev. The code doesn't care.
> >
> > yeah, role is only really useful with a server. Another missing warning.
>
> I think it makes sense only when we can migrate the shared memory
> contents out-of-band. Vaguely
On Fri, Nov 20, 2015 at 03:09:25PM -0700, Eric Blake wrote:
> On 11/20/2015 11:04 AM, Daniel P. Berrange wrote:
> > +
> > +static const char *base64_valid_chars =
> > +"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/=";
> > +
> > +static int
> >
'make check' failed to compile the test case for mingw because of
undefined references. Pull in a few more dependencies so that it builds.
Signed-off-by: Kevin Wolf
---
tests/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/Makefile
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 more dependencies for test-timed-average
test-aio: Fix event notifier
One test case closed an event notifier (event_notifier_cleanup())
without first disabling it (set_event_notifier(..., NULL)). This
resulted in a leftover handle 0 that was added to each subsequent
WaitForMultipleObjects() call, causing the function to fail (invalid
handle).
Signed-off-by: Kevin
On Mon, Nov 23, 2015 at 11:11:28AM +0100, Paolo Bonzini wrote:
>
>
> On 23/11/2015 11:09, Paolo Bonzini wrote:
> > On 23/11/2015 07:41, Pavel Fedin wrote:
> >> Hello! No news for a long time, we are at RC stage. Could we get this in?
> >
> > Yes, queued for -rc2.
>
> ... doh, Eduardo applied
On Thu, Nov 19, 2015 at 10:39:05AM +0800, Xiao Guangrong wrote:
> On 11/19/2015 04:44 AM, Michael S. Tsirkin wrote:
> >On Wed, Nov 18, 2015 at 05:18:17PM -0200, Eduardo Habkost wrote:
> >>On Wed, Nov 18, 2015 at 09:59:34AM +0800, Xiao Guangrong wrote:
> >sorry, I'm busy with 2.5 now, and this is
Connect the SPI devices to Xilinx's ZynqMP.
I also need to make some changes to the actual SPI device to
imporove the fuctionality, but for the time being this works.
V4:
- Rebase
- Rename the SPI busses so that they can all be accessed from the SoC
- Only create one SPI flash device
V3:
-
Connect the sst25wf080 SPI flash to the EP108 board.
Signed-off-by: Alistair Francis
---
V4:
- Only add one SPI flash
V3:
- Don't reach into the SoC
V2:
- Use sst25wf080 instead of m25p80
hw/arm/xlnx-ep108.c | 16
1 file changed, 16
Add the sst25wf080 SPI flash device.
Signed-off-by: Alistair Francis
Reviewed-by: Peter Crosthwaite
---
hw/block/m25p80.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/block/m25p80.c b/hw/block/m25p80.c
index efc43dd..7b9f97c
Move the ssi.h include file into the ssi directory.
While touching the code also fix the typdef lines as
checkpatch complains.
Signed-off-by: Alistair Francis
Reviewed-by: Peter Crosthwaite
---
V2:
- Change git patch to indicate rename
On Mon, Nov 23, 2015 at 10:36:45AM +0100, 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
> >
On 11/23/2015 05:55 PM, Fam Zheng wrote:
> On Mon, 11/23 17:24, Wen Congyang wrote:
>> On 11/23/2015 05:19 PM, Fam Zheng wrote:
>>> On Mon, 11/23 17:01, Wen Congyang wrote:
On 11/20/2015 05:59 PM, Fam Zheng wrote:
> "s->bitmap" tracks done sectors, we only check bit states without using
qmp_query_memdev() has two error paths:
* When object_get_objects_root() returns null. It never does, so
simply drop the useless error handling.
* When query_memdev() fails. It leaks err then. But any failure
there is actually a programming error. Switch it to _abort,
and drop the
On 11/17/2015 08:02 PM, Denis V. Lunev wrote:
From: Vladimir Sementsov-Ogievskiy
This patch marks part of the BAT dirty properly. There is a possibility that
multy-block allocation could have one block allocated on one BAT page and
next block on the next page. The
On Thu, Jul 09, 2015 at 10:56:43AM +0100, Stefan Hajnoczi wrote:
> v2:
> * Default to IOV_MAX instead of INT_MAX [Peter Lieven]
>
> This series depends on "[PATCH] block/mirror: limit qiov to IOV_MAX elements".
>
> IOV_MAX has been hardcoded in several places since preadv()/pwritev()/etc
>
On Wed, Nov 18, 2015 at 03:51:29PM +0100, Kevin Wolf wrote:
> Am 09.07.2015 um 11:56 hat Stefan Hajnoczi geschrieben:
> > v2:
> > * Default to IOV_MAX instead of INT_MAX [Peter Lieven]
> >
> > This series depends on "[PATCH] block/mirror: limit qiov to IOV_MAX
> > elements".
> >
> > IOV_MAX
Connect the Xilinx SPI devices to the ZynqMP model.
Signed-off-by: Alistair Francis
---
V4:
- Rename the SPI busses so that they can all be accessed from the SoC
- Don't set the num-busses property
V3:
- Expose the SPI Bus as part of the SoC device
V2:
- Don't
Seperate out the XilinxSPIPS struct into a seperate header
file.
Signed-off-by: Alistair Francis
---
V4:
- Don't split off R_MOD_ID and hardcode R_MAX
V2:
- Only split out required #defines
- Prefix XLNX_SPIPS_
hw/ssi/xilinx_spips.c | 46
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 DMA API. This idea is
>
> -
On 23/11/2015 07:41, Pavel Fedin wrote:
> Hello! No news for a long time, we are at RC stage. Could we get this in?
Yes, queued for -rc2.
Paolo
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>> -Original Message-
>> From:
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
Marc-André Lureau writes:
> Hi
>
> - Original Message -
>>
>> >> qemu-doc documents role only with chardev. The code doesn't care.
>> >
>> > yeah, role is only really useful with a server. Another missing warning.
>>
>> I think it makes sense only when we can
From: Vladimir Sementsov-Ogievskiy
This specifies Parallels image format as implemented in Parallels Cloud
Server 6.10
Signed-off-by: Vladimir Sementsov-Ogievskiy
Signed-off-by: Denis V. Lunev
CC: Eric Blake
Hi
- Original Message -
> > "role" was designed to only migrate the master. Ability to migrate a pool
> > of
> > peer would be a significant new feature. I am not aware of such request.
>
> I see. But how is this supposed to work?
>
> Before migration: one master and N peers connected
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.json | 3 ++-
qmp-commands.hx | 4 ++--
5 files changed, 11 insertions(+), 7 deletions(-)
This will allow the user specify "-d" (just like command
"migrate") when using "dump-guest-memory" command. When
specified, one background thread is created to do the dump work.
One flag is added to show whether there is a background dump
work in progress.
Signed-off-by: Peter Xu
Marc-André Lureau writes:
> Hi
>
> - Original Message -
>> > "role" was designed to only migrate the master. Ability to migrate a pool
>> > of
>> > peer would be a significant new feature. I am not aware of such request.
>>
>> I see. But how is this supposed to
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.
Graphic plane is connected to the
On Sat, Nov 21, 2015 at 02:09:25AM +0100, Borislav Petkov wrote:
> On Sat, Nov 21, 2015 at 12:11:35AM +0100, Andreas Färber wrote:
> > Hi,
> >
> > CC'ing qemu-devel.
>
> Ah, thanks.
>
> > Am 21.11.2015 um 00:01 schrieb Borislav Petkov:
> > > From: Borislav Petkov
> > >
> > >
remove superfluous code in do_pci_register_device(). See its caller:
pci_qdev_realize()
Signed-off-by: Cao jin
---
hw/pci/pci.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/pci/pci.c b/hw/pci/pci.c
index 168b9cc..4d16da0 100644
--- a/hw/pci/pci.c
+++
"Daniel P. Berrange" writes:
> On Fri, Nov 20, 2015 at 03:09:25PM -0700, Eric Blake wrote:
>> On 11/20/2015 11:04 AM, Daniel P. Berrange wrote:
>> > +
>> > +static const char *base64_valid_chars =
>> > +"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/=";
On 11/23/2015 02:16 PM, Stefan Weil wrote:
Am 23.11.2015 um 13:45 schrieb Richard Henderson:
From: John Clarke
A simple typo in the variable to use when comparing vs the highwater mark.
Reports are that qemu can in fact segfault occasionally due to this mistake.
Currently, dump-guest-memory supports synchronous operation only. This patch
sets are adding "detach" support for it (just like "migrate -d" for
migration). When "-d" is provided, dump-guest-memory command will return
immediately without hanging user. This should be useful when the backend
storage
This will allow the user specify "-d" (just like command
"migrate") when using "dump-guest-memory" command. When
specified, one background thread is created to do the dump work.
One flag is added to show whether there is a background dump
work in progress.
Signed-off-by: Peter Xu
Currently, dump-guest-memory supports synchronous operation only. This patch
sets are adding "detach" support for it (just like "migrate -d" for
migration). When "-d" is provided, dump-guest-memory command will return
immediately without hanging user. This should be useful when the backend
storage
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.json | 3 ++-
qmp-commands.hx | 4 ++--
5 files changed, 11 insertions(+), 7 deletions(-)
Public bug reported:
device_del and drive_del commands don't cause virtio disk detaching
Steps to reproduce:
1. Run instance
2. Attach virtio scsi disk
3. Reboot instance
4. Immediately after reboot detach disk with QEMU commands:
device_del
drive_del
Expected result:
Disk should be detached
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 another thread, aslo here:
>>>
Hi
- Original Message -
> >
> > You can't migrate the peers.
>
> Then explain the case N'=0 to me: how can you migrate the master so that
> it's connected to a server afterwards?
Dest qemu: -incoming.. -chardev socket,path=dest-server
That is, start your destination qemu with a
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.
Thanks,
--Gabriel
On Thu, Nov 05, 2015 at 09:32:46AM -0500, Gabriel L. Somlo wrote:
> New since v4:
>
>
Gives some general guidelines for reporting errors in QEMU.
Signed-off-by: Lluís Vilanova
---
HACKING | 52 ++
include/qapi/error.h | 12
util/error.c | 24 +--
3
On 20/11/2015 18:56, Markus Armbruster wrote:
> Looks rather fishy:
>
> if (strncmp(s->server_chr->filename, "unix:", 5)) {
> error_setg(errp, "chardev is not a unix client socket");
> return;
> }
>
> Paolo, is this reliable?
Yes, though by total chance
On 20/11/2015 18:32, Eric Blake wrote:
> > static void qlist_size_iter(QObject *obj, void *opaque)
> > {
> > size_t *count = opaque;
> > (*count)++;
> > }
>
> Yuck - we don't track size independently? Seems like it might make a
> worthwhile addition,
Would you change your mind, if I
On Mon, 23 Nov 2015 11:52:50 +0200
"Michael S. Tsirkin" wrote:
> On Mon, Nov 23, 2015 at 10:36:45AM +0100, Cornelia Huck wrote:
> > On Mon, 23 Nov 2015 15:41:11 +0800
> > Jason Wang wrote:
> >
> > > Currently, all virtio devices bypass IOMMU completely.
On 23 November 2015 at 14:34, Cornelia Huck wrote:
> The mmio transport is a completely different beast; I'm afraid I don't
> know enough about it to say how it interacts with iommus.
Conceptually, it's just a device that does DMA, I think.
You could in theory put it
On 23/11/2015 01:41, 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
On 23/11/2015 13:39, Kevin Wolf wrote:
> tests/test-timed-average$(EXESUF): tests/test-timed-average.o qemu-timer.o \
> libqemuutil.a stubs/clock-warp.o stubs/cpu-get-icount.o \
> - stubs/notify-event.o stubs/replay.o
> + stubs/notify-event.o stubs/replay.o stubs/mon-is-qmp.o
>
Marc-André Lureau writes:
> Hi
>
> - Original Message -
>> >
>> > You can't migrate the peers.
>>
>> Then explain the case N'=0 to me: how can you migrate the master so that
>> it's connected to a server afterwards?
>
> Dest qemu: -incoming.. -chardev
1 - 100 of 276 matches
Mail list logo