Am 30.07.2013 22:06, schrieb Hervé Poussineau:
> Andreas Färber a écrit :
>> Am 23.07.2013 23:16, schrieb Hervé Poussineau:
>>> }
>>>
>>> -static void i82378_init(DeviceState *dev, I82378State *s)
>>> +static void i82378_realize(DeviceState *dev, Error **errp)
>>> {
>>> -ISABus *isabus = IS
On 07/31/2013 10:48 AM, Stefan Weil wrote:
>>
>> -1) QEMU as a whole is released under the GNU General Public License
>> +1) QEMU as a whole is released under the GNU General Public License,
>> +version 2.
>
> I appreciate these clarifications. For point 1, I suggest
>
> ... version 2 or (at y
Am 31.07.2013 08:19, schrieb Paolo Bonzini:
> 1) The GPL says that "if the Program does not specify a version number
> of this License, you may choose any version ever published by the Free
> Software Foundation". This is not true, QEMU includes parts that are
> v2-only.
>
> 2) Provide a default f
> For example, current qcow2 encryption is vulnerable to a watermarking
> attack.
> http://en.wikipedia.org/wiki/Disk_encryption_theory#Cipher-block_chaining_.28CBC.29
void qcow2_encrypt_sectors(BDRVQcowState *s, int64_t sector_num,
uint8_t *out_buf, const uint8_t *in_bu
My email address in samsung.com domain is no longer accessible, change
it to my personal gmail address.
Signed-off-by: Igor Mitsyanko
---
Currently I can't send patches properly with send-email command, I can only
use gmail web interface for this. I'm not sure that it would apply cleanly
though,
On 07/31/2013 04:39 PM, Michael R. Hines wrote:
> On 07/30/2013 11:31 AM, Orit Wasserman wrote:
>> On 07/30/2013 05:57 PM, Michael R. Hines wrote:
>>> On 07/30/2013 04:14 AM, Orit Wasserman wrote:
On 07/27/2013 05:23 AM, mrhi...@linux.vnet.ibm.com wrote:
> From: "Michael R. Hines"
>
>
On 07/31/13 15:11, Markus Armbruster wrote:
> All I wanted to do is exit(1) instead of abort() on guest memory
> allocation failure [07/08]. But that lead me into a minor #ifdef bog,
> and here's what I brought back. Enjoy!
>
> Testing:
> * Christian Borntraeger reports v1 works fine under LPAR
> Crypto should be done by trained professionals[*].
I agree I feel uneasy to write cryptographic code.
Best regards
Benoît
Move qemu-ga build check out of if softmmu.. into its own section.
We want to build qemu-ga for _guest_ even if system build isn't
done. It is controlled separately using --enable-guest-agent.
Additionally, give error message if guest agent is requested but
not supported.
Signed-off-by: Michael T
Move qemu-ga build check out of if softmmu.. into its own section.
We want to build qemu-ga for _guest_ even if system build isn't
done. It is controlled separately using --enable-guest-agent.
Additionally, give error message if guest agent is requested but
not supported.
Signed-off-by: Michael T
Introduce bdrv_ref/bdrv_unref to manage the lifecycle of
BlockDriverState. They are unused for now but will used to replace
bdrv_delete() later.
Signed-off-by: Fam Zheng
---
block.c | 21 +
include/block/block.h | 2 ++
include/block/block_int.h | 1 +
Ping re 1.5.3
Markus Armbruster writes:
> Watch this:
>
> $ upstream-qemu -nodefaults -S -vnc :0,acl,sasl -monitor stdio
> QEMU 1.5.50 monitor - type 'help' for more information
> (qemu) acl_add vnc.username drei allow
> acl: added rule at position 1
> (qemu) acl_show vnc.use
Am 31.07.2013 um 14:13 hat Paolo Bonzini geschrieben:
> > The documentation patch contains a line like this:
> >
> > 0 131072 2327680
> >
> > A heading line and tabs (or even better, fixed printf column widths)
> > sounds good, but I think if it's really only for human users a
Am 31.07.2013 15:11, schrieb Markus Armbruster:
> We abort() on memory allocation failure. abort() is appropriate for
> programming errors. Maybe most memory allocation failures are
> programming errors, maybe not. But guest memory allocation failure
> isn't, and aborting when the user asks for
Hi Michael,
how this affect 1.5 schedule?? Is the date mentioned on
http://wiki.qemu.org/Planning/1.5 still valid (just increase
the build number)?
Mirek Rezanina
- Original Message -
> From: "Michael Roth"
> To: qemu-devel@nongnu.org
> Cc: pmato...@redhat.com, aligu...@us.ibm.com, ler.
All I wanted to do is exit(1) instead of abort() on guest memory
allocation failure [07/08]. But that lead me into a minor #ifdef bog,
and here's what I brought back. Enjoy!
Testing:
* Christian Borntraeger reports v1 works fine under LPAR (new S390
KVM, i.e. generic allocation) and as second
pc_isa_bios_init() suffers integer overflow for flash larger than
INT_MAX.
Signed-off-by: Markus Armbruster
---
hw/block/pc_sysfw.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/hw/block/pc_sysfw.c b/hw/block/pc_sysfw.c
index 7db68f0..74a5364 100644
--- a/hw/block/pc_sy
We abort() on memory allocation failure. abort() is appropriate for
programming errors. Maybe most memory allocation failures are
programming errors, maybe not. But guest memory allocation failure
isn't, and aborting when the user asks for more memory than we can
provide is not nice. exit(1) in
Make it a generic hook rather than a KVM hook. Less code and
ifdeffery.
Since the only user of the hook is old S390 KVM, there's hope we can
get rid of it some day.
Acked-by: Christian Borntraeger
Signed-off-by: Markus Armbruster
---
exec.c | 19 +--
include/e
On 07/30/2013 11:31 AM, Orit Wasserman wrote:
On 07/30/2013 05:57 PM, Michael R. Hines wrote:
On 07/30/2013 04:14 AM, Orit Wasserman wrote:
On 07/27/2013 05:23 AM, mrhi...@linux.vnet.ibm.com wrote:
From: "Michael R. Hines"
When testing with libvirt, a simple IPv6 migration test failed
becaus
With -mem-path, qemu_ram_alloc_from_ptr() first tries to allocate
accordingly, but when it fails, it falls back to normal allocation.
The fall back allocation code used to be effectively identical to the
"-mem-path not given" code, until it started to diverge in commit
432d268. I believe the code
Ok, but it's unclear how do you prefer to create and "empty"
PC_COMPAT_1_6 in Patch 1.
If you want to keep this declaration form
[...]
.compat_props = (GlobalProperty[]) {
PC_COMPAT_1_6,
{ /* end of list */ }
},
[...]
in the two pc_*_machine_v1_6 structs, I'm forced to define
Another issue missed in commit fdec991 is -mem-path: it needs to be
rejected only for old S390 KVM, not for any S390. Not that I
personally care, but the ifdeffery in qemu_ram_alloc_from_ptr() annoys
me.
Note that this doesn't actually make -mem-path work, as the kernel
doesn't (yet?) support la
Old S390 KVM wants guest RAM mapped in a peculiar way. Commit 6b02494
implemented that.
When qemu_ram_remap() got added in commit cd19cfa, its code carefully
mimicked the allocation code: peculiar way if defined(TARGET_S390X) &&
defined(CONFIG_KVM), else normal way.
For new S390 KVM, we actually
Am 30.07.2013 15:20, schrieb Anthony Liguori:
> Andreas Färber writes:
>
>> Signed-off-by: Andreas Färber
>
> I'm not sure this is heading in the right direction.
>
> What's the bigger picture here? Are we saying that all machines must be
> launchable without any special parameters? If so, c
On 07/31/13 10:50, Markus Armbruster wrote:
> Markus Armbruster writes:
>
>> Ping?
>
> Has been ignored for six weeks, and now it no longer applies. Rebased
> version coming.
>
> *Sigh*
Why haven't you been made a maintainer yet? You could have a
"cleanup-fubars" tree and you could send pull
Issues:
* We try to obey -mem-path even though it can't work with Xen.
* To implement -machine mem-merge, we call
memory_try_enable_merging(new_block->host, size). But with Xen,
new_block->host remains null. Oops.
Fix by separating Xen allocation from normal allocation.
Acked-by: Stefano
On Wed, 31 Jul 2013 14:23:08 +0200
Laszlo Ersek wrote:
> Hi Qiao,
>
> On 07/31/13 11:26, Qiao Nuohan wrote:
> > Hello Luiz and Amos,
> >
> > My patches are waiting for introspection. But now I cannot quite catch
> > the situation of introspection, so I hope to get some information about
> > cur
On Wed, 31 Jul 2013 08:19:51 +0200
Paolo Bonzini wrote:
> Most of the block layer is under the BSD license, thus it is reasonable
> to license block/raw.c the same way. CCed people should ACK by replying
> with a Signed-off-by line.
>
> Cc: Christoph Hellwig
> Cc: Kevin Wolf
> Cc: Anthony Lig
- Original Message -
> From: "Kevin Wolf"
> To: "Paolo Bonzini"
> Cc: qemu-devel@nongnu.org, stefa...@redhat.com, ebl...@redhat.com,
> p...@kamp.de
> Sent: Wednesday, July 31, 2013 11:21:27 AM
> Subject: Re: [PATCH v3 19/19] block: look for zero blocks in bs->file
>
> Am 25.07.2013 um
- Original Message -
> From: "Kevin Wolf"
> To: "Paolo Bonzini"
> Cc: qemu-devel@nongnu.org, stefa...@redhat.com, ebl...@redhat.com,
> p...@kamp.de
> Sent: Wednesday, July 31, 2013 11:12:27 AM
> Subject: Re: [PATCH v3 18/19] block: add default get_block_status
> implementation for pro
31.07.2013 16:03, Andreas Färber wrote:
> Am 31.07.2013 13:05, schrieb Peter Maydell:
>>> Actually the more I think about it... Maybe it shouldn't depend
>>> on --enable-tools either, but should be an independent option.
>>> Because it isn't really a tool.
>>
>> This seems to me to be unnecessarily
On Wed, Jul 31, 2013 at 08:19:51AM +0200, Paolo Bonzini wrote:
> Most of the block layer is under the BSD license, thus it is reasonable
> to license block/raw.c the same way. CCed people should ACK by replying
> with a Signed-off-by line.
>
> Cc: Christoph Hellwig
> Cc: Kevin Wolf
> Cc: Anthon
On 07/31/13 11:10, Gerd Hoffmann wrote:
> Guest trying to reset a endpoint of a disconnected device resulted in
> xhci trying to dereference uport while being NULL, thereby crashing
> qemu. Fix that by adding a check. Drop unused dev variable while
> touching that code bit.
>
> Cc: qemu-sta...@n
On 07/31/13 11:21, Gerd Hoffmann wrote:
> Reinitialize dev->cs to NULL after deleting it, to make sure it isn't
> used afterwards.
>
> Reported-by: Martin Cerveny
> Signed-off-by: Gerd Hoffmann
> ---
> hw/usb/redirect.c |1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/usb/redirec
Hi Qiao,
On 07/31/13 11:26, Qiao Nuohan wrote:
> Hello Luiz and Amos,
>
> My patches are waiting for introspection. But now I cannot quite catch
> the situation of introspection, so I hope to get some information about
> current state from you. It will be very appreciated.
I wasn't aware that yo
> The documentation patch contains a line like this:
>
> 0 131072 2327680
>
> A heading line and tabs (or even better, fixed printf column widths)
> sounds good, but I think if it's really only for human users and not for
> shell scripts, we can further improve the output:
>
(CC'ing qemu-devel)
On 07/16/13 17:12, Borislav Petkov wrote:> (this time after I subscribed to the
ML)
>
> Hi guys,
>
> I've been playing with mapping EFI runtime regions in a topdown manner
> in Linux for purposes of using EFI in a kexec'ed kernel. For that I've
> been using EFI BIOS built from
On 07/30/13 19:13, Hans de Goede wrote:
> Hi,
>
> On 07/22/2013 02:58 PM, Gerd Hoffmann wrote:
>> On 07/16/13 10:45, Gonglei (Arei) wrote:
>>> Hi, Gerd
>>> My Qemu version is 1.5.1, and use libusb for usb pass through.
>>> I pass through a host usb device to the guest by bus number and
>>>
Manage BlockDriverState lifecycle with refcnt, so bdrv_delete() is no
longer public and should be called by bdrv_unref() if refcnt is
decreased to 0.
This is an identical change because effectively, there's no multiple
reference of BDS now: no caller of bdrv_ref() yet, only bdrv_new() sets
bs->ref
Am 31.07.2013 13:05, schrieb Peter Maydell:
> On 31 July 2013 11:27, Michael Tokarev wrote:
>> 31.07.2013 14:24, Michael Tokarev wrote:
>>> Move qemu-ga build check out of if softmmu.. into if tools section.
>>> We want to build qemu-ga for _guest_ even if system build isn't
>>> done. It is contr
Previously, nbd calls drive_get_ref() on the drive of bs. A BDS doesn't
always have associated dinfo, which nbd doesn't care either. We already
have BDS ref count, so use it to make it safe for a BDS w/o blockdev.
Signed-off-by: Fam Zheng
---
blockdev-nbd.c | 10 +-
nbd.c | 5 +
Am 31.07.2013 13:20, schrieb Stefan Hajnoczi:
> On Wed, Jul 31, 2013 at 12:19:06PM +0200, Vincenzo Maffione wrote:
>> Sorry, I'm not confident with this infrastructure.
>
> Thanks for your efforts! Normally this change would not be necessary
> but you are the first person who needs a 1.6 compat p
On Wed, Jul 31, 2013 at 12:19:06PM +0200, Vincenzo Maffione wrote:
> Sorry, I'm not confident with this infrastructure.
Thanks for your efforts! Normally this change would not be necessary
but you are the first person who needs a 1.6 compat property :).
> So do you just want me to invert the com
On 31 July 2013 11:27, Michael Tokarev wrote:
> 31.07.2013 14:24, Michael Tokarev wrote:
>> Move qemu-ga build check out of if softmmu.. into if tools section.
>> We want to build qemu-ga for _guest_ even if system build isn't
>> done. It is controlled separately using --enable-guest-agent.
>
> A
BlockDriverState structure needs bdrv_new() to initialize refcnt, don't
allocate a local structure variable and memset to 0, becasue with coming
refcnt implementation, bdrv_unref will crash if bs->refcnt not
initialized to 1.
Signed-off-by: Fam Zheng
---
block/iscsi.c | 14 +++---
1 file
On 07/31/13 08:42, Wanlong Gao wrote:
> Signed-off-by: Wanlong Gao
> ---
> qapi-schema.json | 47 +++
> 1 file changed, 47 insertions(+)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index a51f7d2..b9b18e4 100644
> --- a/qapi-schema.json
> +++
31.07.2013 14:24, Michael Tokarev wrote:
Move qemu-ga build check out of if softmmu.. into if tools section.
We want to build qemu-ga for _guest_ even if system build isn't
done. It is controlled separately using --enable-guest-agent.
Actually the more I think about it... Maybe it shouldn't de
On Wed, Jul 31, 2013 at 08:19:51AM +0200, Paolo Bonzini wrote:
> Most of the block layer is under the BSD license, thus it is reasonable
> to license block/raw.c the same way. CCed people should ACK by replying
> with a Signed-off-by line.
>
> Cc: Christoph Hellwig
> Cc: Kevin Wolf
> Cc: Anthon
Move qemu-ga build check out of if softmmu.. into if tools section.
We want to build qemu-ga for _guest_ even if system build isn't
done. It is controlled separately using --enable-guest-agent.
Signed-off-by: Michael Tokarev
---
configure |8 +++-
1 file changed, 3 insertions(+), 5 dele
block-migration.c does not actually use DriveInfo anywhere. Hence it's
safe to drive ref code, we really only care about referencing BDS.
Signed-off-by: Fam Zheng
---
block-migration.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block-migration.c b/block-migration.c
Sorry, I'm not confident with this infrastructure.
So do you just want me to invert the commit order? (and do the other
two little changes)
Thanks,
Vincenzo
2013/7/31 Andreas Färber :
> Am 31.07.2013 10:13, schrieb Vincenzo Maffione:
>> Implement interrupt mitigation for the e1000 device with
we need bdrv_new() to properly initialize BDS, don't allocate memory
manually.
Signed-off-by: Fam Zheng
---
block/vvfat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/vvfat.c b/block/vvfat.c
index cd3b8ed..a827d91 100644
--- a/block/vvfat.c
+++ b/block/vvfat.c
@@ -29
BlockDriverState lifecycle management is needed by future features such as
image fleecing and blockdev-add. This series adds reference count to
BlockDriverState.
The first two patches clean up two odd BlockDriverState use cases, so all code
uses bdrv_new() to create BlockDriverState instance.
The
Am 31.07.2013 10:13, schrieb Vincenzo Maffione:
> This patch partially implements the e1000 interrupt mitigation mechanisms.
> Using a single QEMUTimer, it emulates the ITR register (which is the newer
> mitigation register, recommended by Intel) and approximately emulates
> RADV and TADV registers
Am 31.07.2013 10:13, schrieb Vincenzo Maffione:
> diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
> index 3a0c4e3..812df4d 100644
> --- a/include/hw/i386/pc.h
> +++ b/include/hw/i386/pc.h
> @@ -214,6 +214,13 @@ void pvpanic_init(ISABus *bus);
>
> int e820_add_entry(uint64_t, uint64_t, u
Am 31.07.2013 10:13, schrieb Vincenzo Maffione:
> Implement interrupt mitigation for the e1000 device with the
> corresponding "mitigation" device property.
>
> Add a compat_props entry to pc-1.6 machines in order to set the
> "mitigation" property for these machines.
>
> Vincenzo Maffione (2):
>
On Tue, 07/30 16:58, Stefan Hajnoczi wrote:
> On Tue, Jul 30, 2013 at 03:52:53PM +0800, Fam Zheng wrote:
> > @@ -1518,6 +1519,9 @@ static void bdrv_move_feature_fields(BlockDriverState
> > *bs_dest,
> > /* dirty bitmap */
> > bs_dest->dirty_bitmap = bs_src->dirty_bitmap;
> >
> >
Hello Luiz and Amos,
My patches are waiting for introspection. But now I cannot quite catch the
situation of introspection, so I hope to get some information about current
state from you. It will be very appreciated.
On 07/09/2013 03:36 PM, Qiao Nuohan wrote:
On 07/09/2013 03:30 PM, Qiao Nu
Reinitialize dev->cs to NULL after deleting it, to make sure it isn't
used afterwards.
Reported-by: Martin Cerveny
Signed-off-by: Gerd Hoffmann
---
hw/usb/redirect.c |1 +
1 file changed, 1 insertion(+)
diff --git a/hw/usb/redirect.c b/hw/usb/redirect.c
index 8b8c010..e3b9f32 100644
--- a/
Hi,
> diff --git a/hw/usb/redirect.c b/hw/usb/redirect.c
> index a594e95..1c62263 100644
> --- a/hw/usb/redirect.c
> +++ b/hw/usb/redirect.c
> @@ -1334,6 +1334,7 @@ static void usbredir_handle_destroy(USBDevice *udev)
> USBRedirDevice *dev = DO_UPCAST(USBRedirDevice, dev, udev);
>
> q
Am 25.07.2013 um 16:23 hat Paolo Bonzini geschrieben:
> Reviewed-by: Eric Blake
> Signed-off-by: Paolo Bonzini
> ---
> block.c | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/block.c b/block.c
> index 8738937..1493f22 100644
> --- a/block.c
> +++ b/block.c
> @
Guest trying to reset a endpoint of a disconnected device resulted in
xhci trying to dereference uport while being NULL, thereby crashing
qemu. Fix that by adding a check. Drop unused dev variable while
touching that code bit.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Gerd Hoffmann
---
hw/usb/
Am 25.07.2013 um 16:23 hat Paolo Bonzini geschrieben:
> Alternatively, this could use a "discard zeroes data" flag returned
> by bdrv_get_info.
>
> Reviewed-by: Eric Blake
> Signed-off-by: Paolo Bonzini
> ---
> block.c | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --g
PC_COMPAT_1_6 macro introduced in order to set the e1000
"mitigation" property off for pc-i440fx-1.6 and pc-q35-1.6
machines.
Signed-off-by: Vincenzo Maffione
---
hw/i386/pc_piix.c| 4
hw/i386/pc_q35.c | 4
include/hw/i386/pc.h | 7 +++
3 files changed, 15 insertions(+)
di
Am 25.07.2013 um 16:23 hat Paolo Bonzini geschrieben:
> Protocols return raw data, so you can assume the offsets to pass
> through unchanged.
>
> Reviewed-by: Eric Blake
> Signed-off-by: Paolo Bonzini
Not really objecting, but is this useful?
In formats, BDRV_BLOCK_OFFSET_VALID means that the
Implement interrupt mitigation for the e1000 device with the
corresponding "mitigation" device property.
Add a compat_props entry to pc-1.6 machines in order to set the
"mitigation" property for these machines.
Vincenzo Maffione (2):
e1000: add interrupt mitigation support
i386/pc: introducin
Am 31.07.2013 08:54, schrieb Michal Novotny:
> there are
> still some code parts that are not using error_report() as well, e.g.
>
> fprintf(stderr, "Error: standard VGA not available\n");
>
> in the select_vgahw() function (line 2168) or:
>
> fprintf(stderr, "Failed to start VNC ser
On Mon, 29 Jul 2013 15:59:53 +0200
Jens Freimann wrote:
> This patch adds a floating irq controller as a kvm_device.
> It will be necesary for migration of floating interrupts as well
> as for hardening the reset code by allowing user space to explicitly
> remove all pending floating interrupts.
On Mon, Jul 29, 2013 at 10:58:40AM +0200, Kevin Wolf wrote:
> Am 26.07.2013 um 10:43 hat Stefan Hajnoczi geschrieben:
> > On Thu, Jul 25, 2013 at 07:53:33PM +0100, Alex Bligh wrote:
> > >
> > >
> > > --On 25 July 2013 14:32:59 +0200 Jan Kiszka
> > > wrote:
> > >
> > > >>I would happily at a QE
Michal Novotny writes:
> On 07/31/2013 08:45 AM, Markus Armbruster wrote:
>> Michal Novotny writes:
>>
>>> Output error message to stderr when user provides the invalid machine
>>> type on the command line. This also saves time to find what issue is
>>> when you downgrade from one version of qem
Am 30.07.2013 um 17:22 hat Paolo Bonzini geschrieben:
> Il 30/07/2013 17:13, Kevin Wolf ha scritto:
> > Am 25.07.2013 um 16:23 hat Paolo Bonzini geschrieben:
> >> This command dumps the metadata of an entire chain, in either tabular or
> >> JSON
> >> format.
> >>
> >> Signed-off-by: Paolo Bonzini
Markus Armbruster writes:
> Ping?
Has been ignored for six weeks, and now it no longer applies. Rebased
version coming.
*Sigh*
On Tue, Jul 30, 2013 at 11:27:04AM +0200, Gabriele Paciucci wrote:
> I'm new for this ml, sorry if this mail is not in the right place!!!
>
> I'm looking for standard benchmarks to test VMs.
> I have seen several presentations from IBM and Red Hat using FFSB. Is there a
> "widely used" configura
Am 30.07.2013 um 19:44 hat Luiz Capitulino geschrieben:
> On Fri, 26 Jul 2013 20:14:06 +0200
> Kevin Wolf wrote:
>
> > Am 26.07.2013 um 19:45 hat Eric Blake geschrieben:
> > > Overall, I like where this is headed, but I'm not quite sure it is ready
> > > for commit as-is; looking forward to v2.
Paolo Bonzini writes:
> Most of the block layer is under the BSD license, thus it is reasonable
> to license block/raw.c the same way. CCed people should ACK by replying
> with a Signed-off-by line.
>
> Cc: Christoph Hellwig
> Cc: Kevin Wolf
> Cc: Anthony Liguori
> Cc: Markus Armbruster
> Cc
Am 31.07.2013 um 08:19 hat Paolo Bonzini geschrieben:
> Most of the block layer is under the BSD license, thus it is reasonable
> to license block/raw.c the same way. CCed people should ACK by replying
> with a Signed-off-by line.
>
> Cc: Christoph Hellwig
> Cc: Kevin Wolf
> Cc: Anthony Liguori
Anthony,
Am 30.07.2013 20:20, schrieb Richard Henderson:
> Signed-off-by: Richard Henderson
FWIW
Reviewed-by: Andreas Färber
This is a build fix, can you please review and apply 1/2?
2/2 was outside my quick understanding so I'm not sure. ;)
rth, you forgot to mark it "for-1.6".
Regards,
An
Am 31.07.2013 07:00, schrieb Stefan Weil:
> Shifting a long int (32 bit) by 40 bit positions won't work.
> Compiler message:
>
> hw/core/qdev-properties.c: In function ‘print_size’:
> hw/core/qdev-properties.c:1180:5: warning: left shift count >= width of type
>
> Signed-off-by: Stefan Weil
> --
Am 31.07.2013 08:19, schrieb Paolo Bonzini:
> 1) The GPL says that "if the Program does not specify a version number
> of this License, you may choose any version ever published by the Free
> Software Foundation". This is not true, QEMU includes parts that are
> v2-only.
>
> 2) Provide a default
Paolo Bonzini wrote:
> 4) Restrict GPLv2-only contributions to user mode emulation (due to
> code from Linux) and PCI passthrough (due to code from Neocleus).
It would be nice to have that statement or something like it
mentioning the linux-user/ tree added to the LICENSE file.
Cheers,
Erik
--
On 07/31/2013 08:45 AM, Markus Armbruster wrote:
> Michal Novotny writes:
>
>> Output error message to stderr when user provides the invalid machine
>> type on the command line. This also saves time to find what issue is
>> when you downgrade from one version of qemu to another that doesn't
>> su
On 07/31/2013 08:45 AM, Markus Armbruster wrote:
> Michal Novotny writes:
>
>> Output error message to stderr when user provides the invalid machine
>> type on the command line. This also saves time to find what issue is
>> when you downgrade from one version of qemu to another that doesn't
>> sup
Output error message using qemu's error_report() function when user
provides the invalid machine type on the command line. This also saves
time to find what issue is when you downgrade from one version of qemu
to another that doesn't support required machine type yet (the version
user downgraded to
Add the numa_info structure to contain the numa nodes memory,
VCPUs information and the future added numa nodes host memory
policies.
Reviewed-by: Eduardo Habkost
Signed-off-by: Andre Przywara
Signed-off-by: Wanlong Gao
---
hw/i386/pc.c| 4 ++--
include/sysemu/sysemu.h | 8 ++
On Tue, 2013-07-30 at 22:41 +0200, Stefan Weil wrote:
> The definition of macro BIT in tci/tcg-target.c now conflicts with the
> definition of the same macro in includes qemu/bitops.h.
>
> This conflict was triggered by a recent change in the include chain of
> tcg.c (probably commit 949fc82314cc8
Add qmp command query-numa to show guest NUMA information.
Signed-off-by: Wanlong Gao
---
numa.c | 69
qapi-schema.json | 36 +
qmp-commands.hx | 49
3 files c
101 - 187 of 187 matches
Mail list logo
