Signed-off-by: Chen Fan
---
target-i386/cpu.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 6d008ab..217500c 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1716,9 +1716,9 @@ static void x86_set_hv_spinlocks(O
On Fri, 25 Jul 2014 19:56:40 +0200
Laszlo Ersek wrote:
> On 07/25/14 17:48, Igor Mammedov wrote:
>
> > Add API to mark memory region as extend-able on migration,
> > to allow migration code to load smaller RAMBlock into
> > a bigger one on destination QEMU instance.
> >
> > This will allow to fi
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Il 17/07/2014 13:01, Pavel Dovgalyuk ha scritto:
> > This set of patches is related to the reverse execution and deterministic
> > replay of qemu execution Our implementation of deterministic replay can
> > be u
> Am 28.07.2014 um 08:47 schrieb Alexey Kardashevskiy :
>
>> On 07/24/2014 11:15 PM, Alexander Graf wrote:
>>
>>> On 18.07.14 06:31, cyril...@gmail.com wrote:
>>> It may prove useful know which Linux distribution version the host machine
>>> is running when an issue in the guest arises but a us
On Fri, 25 Jul 2014 19:37:41 +0200
Paolo Bonzini wrote:
> Il 25/07/2014 17:48, Igor Mammedov ha scritto:
> > It fixes migration failure for machine type pc-i440fx-1.7 from
> > QEMU 1.7/2.0 to QEMU 2.1
> >
> > Migration fails due to ACPI tables size grows across 1.7-2.1
> > versions. That causes
Changes since v2:
- addressed Laszlo's comments
* fixing typos, rewording comments
* dropping enum-ification of RAMBlock flags
* adding zeroing out destination ramblock
* replacing 'if' with assert()
Changing the ACPI table size causes migration to break, and the memory
Add API to mark memory region as extend-able on migration,
to allow migration code to load smaller RAMBlock into
a bigger one on destination QEMU instance.
This will allow to fix broken migration from QEMU 1.7/2.0 to
QEMU 2.1 due to ACPI tables size changes across 1.7/2.0/2.1
versions by marking
It fixes migration failure for machine type pc-i440fx-1.7 from
QEMU 1.7/2.0 to QEMU 2.1
Migration fails due to ACPI tables size grows across 1.7-2.1
versions. That causes ACPI tables ROM blob to change its size
differently for the same configurations on different QEMU versions.
As result migration
On Mon, 28 Jul 2014 15:13:06 +0800
Chen Fan wrote:
> Signed-off-by: Chen Fan
> ---
> target-i386/cpu.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index 6d008ab..217500c 100644
> --- a/target-i386/cpu.c
> +++ b/tar
On 07/28/14 09:40, Igor Mammedov wrote:
> On Fri, 25 Jul 2014 19:56:40 +0200
> Laszlo Ersek wrote:
>
>> On 07/25/14 17:48, Igor Mammedov wrote:
>>
>>> Add API to mark memory region as extend-able on migration,
>>> to allow migration code to load smaller RAMBlock into
>>> a bigger one on destinati
Il 27/07/2014 08:57, Jan Kiszka ha scritto:
> From: Jan Kiszka
>
> According to ICH9 spec, the MSI capability is located at 0x60. This is
> important for guest drivers that do not parse the capability chain and
> use absolute addresses instead.
>
> Signed-off-by: Jan Kiszka
> ---
> hw/audio/in
Il 27/07/2014 09:08, Jan Kiszka ha scritto:
> From: Jan Kiszka
>
> The spec says (and real HW confirms this) that, if the bus master bit
> is 0, the device will not generate any PCI accesses. MSI and MSI-X
> messages fall among these, so we should use the corresponding address
> space to deliver
On 2014-07-28 10:11, Paolo Bonzini wrote:
> Il 27/07/2014 08:57, Jan Kiszka ha scritto:
>> From: Jan Kiszka
>>
>> According to ICH9 spec, the MSI capability is located at 0x60. This is
>> important for guest drivers that do not parse the capability chain and
>> use absolute addresses instead.
>>
>
Il 28/07/2014 09:56, Igor Mammedov ha scritto:
>> > It doesn't handle the case of ACPI tables that shrink, which can happen
>> > as well. I guess if this ever happens we can just hard-code the table
>> > size of the "old" versions to something big enough (64K?) and keep using
>> > fine-grained siz
On 07/28/14 10:03, Igor Mammedov wrote:
> Add API to mark memory region as extend-able on migration,
> to allow migration code to load smaller RAMBlock into
> a bigger one on destination QEMU instance.
>
> This will allow to fix broken migration from QEMU 1.7/2.0 to
> QEMU 2.1 due to ACPI tables
Hey,
Yup, thanks, task closed ;-)
Best regards,
Mateusz Krzywicki
From: arei.gong...@huawei.com
To: mateusz.krzywi...@windowslive.com; qemu-devel@nongnu.org
CC: stefa...@redhat.com; kw...@redhat.com
Subject: RE: [Qemu-devel] Possible null-ptr dereference
Date: Mon, 28 Jul 2014 06:03:45 +
Hi,
> > ... because you can just copy the suffix from the old entry here,
> > instead of expecting the caller pass it in.
> >
> Okay, agreed.
>
> But we should also think about the situation which a device don't have
> old entry in global fw_boot_order list.
Throw an error?
I think it is ok
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> VM clock does not run while saving, so there is no need for saving the ticks
> in HPET. Also added saving of hpet_offset field.
>
> Signed-off-by: Pavel Dovgalyuk
> ---
> hw/timer/hpet.c | 13 +
> 1 files changed, 1 insertions(+),
> -Original Message-
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Monday, July 28, 2014 4:31 PM
> Subject: Re: [PATCH v2 1/7] bootindex: add modify_boot_device_path function
>
> Hi,
>
> > > ... because you can just copy the suffix from the old entry here,
> > > instead of ex
On Mon, 28 Jul 2014 08:03:25 +
Igor Mammedov wrote:
> It fixes migration failure for machine type pc-i440fx-1.7 from
> QEMU 1.7/2.0 to QEMU 2.1
>
> Migration fails due to ACPI tables size grows across 1.7-2.1
> versions. That causes ACPI tables ROM blob to change its size
> differently for t
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> vapic state should not be synchronized with APIC while loading,
> because APIC state could be not loaded yet at that moment.
> We just save vapic_paddr in APIC VMState instead of synchronization.
This comment is now obsolete:
include/hw/i386/apic
ping...
All the 6 patches have reviewed-by now.
On Fri, Jul 11, 2014 at 02:09:57PM +0800, Hu Tao wrote:
> This series adds two preallocation mode to qcow2 and raw:
>
> Option preallocation=full preallocates disk space for image by writing
> zeros to disk, this ensures disk space in any cases.
>
It fixes migration failure for machine type pc-i440fx-1.7 from
QEMU 1.7/2.0 to QEMU 2.1
Migration fails due to ACPI tables size grows across 1.7-2.1
versions. That causes ACPI tables ROM blob to change its size
differently for the same configurations on different QEMU versions.
As result migration
On Fri, Jul 25, 2014 at 07:01:47PM +0200, Marc Marí wrote:
> > > @@ -73,3 +97,11 @@ QVirtioPCIDevice
> > > *qvirtio_pci_device_find(QPCIBus *bus, uint16_t device_type)
> > > return dev;
> > > }
> > > +
> > > +void qvirtio_pci_enable_device(QVirtioPCIDevice *d)
> > > +{
> > > +qpci_device
> > I think it is ok to allow only *changing* the bootindex.
> >
> Yes, that's no problem.
But then yoy always will have a old entry where you can take the suffix
from, and you don't need the suffix as parameter for the monitor
command.
cheers,
Gerd
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> This patch adds outport to VMState to allow correct saving and restoring
> the state of PC keyboard controller.
>
> Signed-off-by: Pavel Dovgalyuk
> ---
> hw/input/pckbd.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff
Hi,
> -Original Message-
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Monday, July 28, 2014 5:28 PM
> Subject: Re: [PATCH v2 1/7] bootindex: add modify_boot_device_path function
>
> > > I think it is ok to allow only *changing* the bootindex.
> > >
> > Yes, that's no problem.
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> This patch adds virtual clock-dependent timers to VMState to allow correct
> saving and restoring the state of RTL8139 network controller.
>
> Signed-off-by: Pavel Dovgalyuk
> ---
> hw/net/rtl8139.c |5 -
> 1 files changed, 4 insertions(
Il 17/07/2014 13:03, Pavel Dovgalyuk ha scritto:
> This patch adds irq_reinject_on_ack_count field to VMState to allow correct
> saving/loading the state of MC146818 RTC.
>
> Signed-off-by: Pavel Dovgalyuk
> ---
> hw/timer/mc146818rtc.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> VMState added by this patch preserves correct
> loading of the FDC device state.
>
> Signed-off-by: Pavel Dovgalyuk
> ---
> hw/block/fdc.c | 11 +--
> 1 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/hw/block/fdc.c b/
On Mon, Jul 28, 2014 at 06:03:45AM +, Gonglei (Arei) wrote:
> Hi,
>
> Should be easy to fix though. Does the following help?
>
> (Cc'ing Stefan & Kevin)
>
> -->
> xen_disk: fix possible null-ptr dereference
>
> Signed-off-by: Gonglei
> ---
> hw/block/xen_disk.c | 1 +
> 1 file changed, 1 i
> -Original Message-
> From: Stefan Hajnoczi [mailto:stefa...@redhat.com]
> Sent: Monday, July 28, 2014 5:49 PM
> To: Gonglei (Arei)
> Cc: mateusz.krzywi...@windowslive.com; qemu-devel@nongnu.org;
> kw...@redhat.com
> Subject: Re: [Qemu-devel] Possible null-ptr dereference
>
> On Mon, Jul
> From: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] On Behalf Of Paolo
> Bonzini
> Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> > This patch adds virtual clock-dependent timers to VMState to allow correct
> > saving and restoring the state of RTL8139 network controller.
> >
> > Signed-off
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> -.version_id = 3,
> +.version_id = 4,
> .minimum_version_id = 2,
> .pre_save = serial_pre_save,
> .post_load = serial_post_load,
> .fields = (VMStateField[]) {
> VMSTATE_UINT16_V(divider, SerialState, 2),
>
On 28 July 2014 10:49, Stefan Hajnoczi wrote:
> On Mon, Jul 28, 2014 at 06:03:45AM +, Gonglei (Arei) wrote:
>> Hi,
>>
>> Should be easy to fix though. Does the following help?
>>
>> (Cc'ing Stefan & Kevin)
>>
>> -->
>> xen_disk: fix possible null-ptr dereference
>>
>> Signed-off-by: Gonglei
Il 17/07/2014 13:02, Pavel Dovgalyuk ha scritto:
> +.fields = (VMStateField []) {
> +VMSTATE_UINT8(state.dataw, ISAParallelState),
> +VMSTATE_UINT8(state.datar, ISAParallelState),
> +VMSTATE_UINT8(state.status, ISAParallelState),
> +VMSTATE_UINT8(state.contr
Hi,
> > > > I think it is ok to allow only *changing* the bootindex.
> > > >
> > > Yes, that's no problem.
> >
> > But then yoy always will have a old entry where you can take the suffix
> > from, and you don't need the suffix as parameter for the monitor
> > command.
> >
> No, optional.
>
Il 28/07/2014 11:54, Pavel Dovgaluk ha scritto:
>>> > > +VMSTATE_TIMER_V(timer, RTL8139State, 5),
>> >
>> > timer need not be migrated, because it is reinstated by rtl8139_post_load.
>> >
> That's true for normal execution.
> In replay execution mode post_load can be called before cac
Il 28/07/2014 09:50, Pavel Dovgaluk ha scritto:
>> - patches 2 to 13 probably should try to use subsections, so that VMs
>> that do not use the devices try not to save the extra data and keep
>> backwards migration compatibility (at least try to)
>
> Could you give me and example?
> As I know, s
> -Original Message-
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Monday, July 28, 2014 6:02 PM
> Subject: Re: [PATCH v2 1/7] bootindex: add modify_boot_device_path function
>
> Hi,
>
> > > > > I think it is ok to allow only *changing* the bootindex.
> > > > >
> > > > Yes, t
El Fri, 25 Jul 2014 23:37:43 +0200
Marc Marí escribió:
> +
> +data = g_malloc0(512);
> +memread(r_req+16, data, 512);
> +g_assert_cmpstr(data, ==, "TEST");
> +g_free(data);
> +
guest_free() for both requests should be added here. Will be added for
v3
> +/* End test */
> +
On 26 July 2014 08:18, Michael Tokarev wrote:
> There's just one trivial patch this time, fixing another
> occurence of "allows to" in help text. Please consider
> applying for 2.1.
>
> Thanks,
>
> /mjt
>
> The following changes since commit c60a57ff497667780132a3fcdc1500c83af5d5c0:
>
> Merge r
On 25.07.14 08:52, arei.gong...@huawei.com wrote:
From: Gonglei
get_boot_devices_list() will malloc memory, spapr_finalize_fdt
doesn't free it.
Signed-off-by: Chenliang
Signed-off-by: Gonglei
Thanks, applied to ppc-next-2.2.
Alex
On 21.07.14 05:15, Alexey Kardashevskiy wrote:
On 07/03/2014 01:10 PM, Alexey Kardashevskiy wrote:
c4177479 "spapr: make sure RMA is in first mode of first memory node"
introduced regression which prevents from running guests with memoryless
NUMA node#0 which may happen on real POWER8 boxes and
On 21.07.14 05:02, Alexey Kardashevskiy wrote:
At the moment RTAS and device tree are located at 256MB max
which leaves too little space for huge initramdisk images and kernels.
This relaxes the limitation.
This is checkpatch.pl'ed version of:
[PATCH 1/2] loader: Add load_image_size() to replac
MIPS registers an unassigned access handler which raises a guest bus
error exception. However this causes QEMU to crash when KVM is enabled
as it isn't called from the main execution loop so longjmp() gets called
without a corresponding setjmp().
Until the KVM API can be updated to trigger a guest
When trying to print data to the pty, we first check if it is connected.
If not, we try to reconnect, but we drop the pending data even if we
have successfully reconnected; this makes us lose the first byte of the very
first transmission.
This small fix addresses the issue by checking once more if
On Thu, Jul 24, 2014 at 04:32:09PM +0200, Paolo Bonzini wrote:
> Changing the ACPI table size causes migration to break, and the memory
> hotplug work opened our eyes on how horribly we were breaking things in
> 2.0 already.
>
> The ACPI table size is rounded to the next 4k, which one would think
Hi,
As it was posted earlier the output of reading /proc/self/maps is not
correct for a guest. There are some issues:
https://bugs.launchpad.net/qemu/+bug/1346784
http://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg03085.html
http://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg0279
Il 28/07/2014 13:45, Michael S. Tsirkin ha scritto:
>> +/* These are used to size the ACPI tables for -M pc-i440fx-1.7 and
>> + * -M pc-i440fx-2.0.
>
> Let's just say 2.0 and earlier?
This would give the idea that 1.6 is broken, but it isn't.
>> Even if the actual amount of AML generated grows
On 16.07.14 02:20, Gavin Shan wrote:
From: Alexey Kardashevskiy
This makes find_phb()/find_dev() public and changed its names
to spapr_pci_find_phb()/spapr_pci_find_dev() as they are going to
be used from other parts of QEMU such as VFIO DDW (dynamic DMA window)
or VFIO PCI error injection or
On 16.07.14 03:40, Gavin Shan wrote:
On Wed, Jul 16, 2014 at 11:32:13AM +1000, Alexey Kardashevskiy wrote:
On 07/16/2014 11:16 AM, Gavin Shan wrote:
On Wed, Jul 16, 2014 at 11:09:44AM +1000, Alexey Kardashevskiy wrote:
On 07/16/2014 10:20 AM, Gavin Shan wrote:
This updates kernel header (vfi
Il 28/07/2014 13:39, Sebastian Tanase ha scritto:
> When trying to print data to the pty, we first check if it is connected.
> If not, we try to reconnect, but we drop the pending data even if we
> have successfully reconnected; this makes us lose the first byte of the very
> first transmission.
>
Peter Maydell wrote:
> On 25 July 2014 15:22, Paolo Bonzini wrote:
>> Since Igor hasn't sent his patches, and I'm leaving the office, I pushed
>> this to
>>
>>git://github.com/bonzini/qemu.git tags/for-upstream-full
>>
>> I don't know about tests/acpi-test-data/pc. It makes sense that this
>
On Fri, Jul 18, 2014 at 10:15 AM, Slava Pestov
wrote:
> Public bug reported:
>
> If the list of requests passed to multiwrite_merge() contains two
> requests where the first is for a range of sectors that is a strict
> subset of the second's, the second request is truncated to end where the
> firs
On Mon, 28 Jul 2014 14:59:26 +0200
Juan Quintela wrote:
> Peter Maydell wrote:
> > On 25 July 2014 15:22, Paolo Bonzini wrote:
> >> Since Igor hasn't sent his patches, and I'm leaving the office, I pushed
> >> this to
> >>
> >>git://github.com/bonzini/qemu.git tags/for-upstream-full
> >>
>
On 14.07.14 11:15, Bharat Bhushan wrote:
This patchset add support for
- software breakpoint
- h/w breakpoint
- h/w watchpoint
Please find description in individual patch.
Thanks, applied (with minor edits in comments) to ppc-next-2.2.
Alex
On 27.06.14 08:47, Nikunj A Dadhania wrote:
MAX_CPUS 256 is inconsistent with qemu supporting upto 255 cpus. This
MAX_CPUS number was percolated back to "virsh capabilities" with wrong
max_cpus.
Signed-off-by: Nikunj A Dadhania
Nice one :). Thanks, applied to ppc-next-2.2.
Alex
On 10.07.14 15:27, David Hildenbrand wrote:
This is the qemu part of kernel series "Let user space control the
cpu states"
Christian Borntraeger (1):
update linux headers with with cpustate changes
David Hildenbrand (4):
s390x/kvm: introduce proper states for s390 cpus
s390x/kvm: prop
On 28.07.2014, at 15:43, Alexander Graf wrote:
>
> On 10.07.14 15:27, David Hildenbrand wrote:
This is the qemu part of kernel series "Let user space control the
cpu states"
Christian Borntraeger (1):
update linux headers with with cpustate changes
David H
On 10.07.14 15:10, Christian Borntraeger wrote:
From: David Hildenbrand
If a cpu is stopped, it must never be allowed to run and no interrupt may wake
it
up. A cpu also has to be unhalted if it is halted and has work to do - this
scenario wasn't hit in kvm case yet, as only "disabled wait" is
On 07/28/2014 10:49 PM, Alexander Graf wrote:
>
> On 16.07.14 02:20, Gavin Shan wrote:
>> From: Alexey Kardashevskiy
>>
>> This makes find_phb()/find_dev() public and changed its names
>> to spapr_pci_find_phb()/spapr_pci_find_dev() as they are going to
>> be used from other parts of QEMU such as
v2->v3:
fix tests/acpi-test-data/pc/DSDT [Peter]
track down "make check" failure, fix it [patch 4, me]
split patch 2 in two parts [mst]
do not make bsel_alloc global [mst]
include Igor's bridge patch [mst, as discussed on IRC]
Igor Mammedov (1):
pc: acpi:
This replaces the _PRT constant with a method that computes it.
The problem is that the DSDT+SSDT have grown from 2.0 to 2.1,
enough to cross the 8k barrier (we align the ACPI tables to 4k
before putting them in fw_cfg). This causes problems with
migration and the pc-i440fx-2.0 machine type.
The
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In practice this is not the case, because the user
This patch avoids that similar changes break QEMU again in the future.
QEMU will now hard-code 64k as the maximum ACPI table size, which
(despite being an order of magnitude smaller than 640k) should be enough
for everyone.
Reviewed-by: Laszlo Ersek
Tested-by: Igor Mammedov
Signed-off-by: Paolo
My version of IASL (from RHEL7) puts two newlines between the head comment
and the DefinitionBlock property. One was already removed because the
test uses sizeof instead of strlen, but the extra one breaks the detection
of DefinitionBlock. Killing all newlines after the comment drops the
warning.
From: Igor Mammedov
Fixes migration regression from QEMU-1.7 to a newer QEMUs.
SSDT table size in QEMU-1.7 doesn't change regardless of
a number of PCI bridge devices present at startup.
However in QEMU-2.0 since addition of hotplug on PCI bridges,
each PCI bridge adds ~1875 bytes to SSDT table,
On 03.07.14 22:18, Michael S. Tsirkin wrote:
On Thu, Jul 03, 2014 at 08:00:04PM +0200, Alexander Graf wrote:
On 03.07.14 19:57, Peter Maydell wrote:
On 3 July 2014 18:39, Alexander Graf wrote:
Mac OS X reads ICR on every interrupt. When the IRQ line is shared, this may
result in a race where
>
> On 10.07.14 15:10, Christian Borntraeger wrote:
> > From: David Hildenbrand
> >
> > If a cpu is stopped, it must never be allowed to run and no interrupt may
> > wake it
> > up. A cpu also has to be unhalted if it is halted and has work to do - this
> > scenario wasn't hit in kvm case yet, a
Il 28/07/2014 16:16, David Hildenbrand ha scritto:
> Later, another vcpu might decide to turn that vcpu back on (by e.g. sending a
> SIGP START to that vcpu).
>
> I am not sure if such a mechanism/scenario is applicable to any other arch.
> They
> all seem to reset the cs->halted flag if they kno
On 28.07.2014, at 16:16, David Hildenbrand wrote:
>>
>> On 10.07.14 15:10, Christian Borntraeger wrote:
>>> From: David Hildenbrand
>>>
>>> If a cpu is stopped, it must never be allowed to run and no interrupt may
>>> wake it
>>> up. A cpu also has to be unhalted if it is halted and has work
>
> On 28.07.2014, at 16:16, David Hildenbrand wrote:
>
> >>
> >> On 10.07.14 15:10, Christian Borntraeger wrote:
> >>> From: David Hildenbrand
> >>>
> >>> If a cpu is stopped, it must never be allowed to run and no interrupt may
> >>> wake it
> >>> up. A cpu also has to be unhalted if it is
On Mon, Jul 28, 2014 at 04:02:12PM +0200, Paolo Bonzini wrote:
> Changing the ACPI table size causes migration to break, and the memory
> hotplug work opened our eyes on how horribly we were breaking things in
> 2.0 already.
>
> The ACPI table size is rounded to the next 4k, which one would think
Il 28/07/2014 17:05, Michael S. Tsirkin ha scritto:
>> > +/* These are used to size the ACPI tables for -M pc-i440fx-1.7 and
>> > + * -M pc-i440fx-2.0. Even if the actual amount of AML generated grows
>> > + * a little bit, there should be plenty of free space since the DSDT
>> > + * shrunk by ~1.
The per-SCSIDevice parse_cdb callback must not be called if the
request will go through special SCSIReqOps, so detect the special
cases early enough.
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-bus.c | 51 ++-
1 file changed, 30 insertions(+), 21
Right now scsi-generic is parsing the CDB, in order to compute
the expected number of bytes to be transferred. This is necessary
if DMA is done by the HBA via scsi_req_data, but it prevents executing
vendor-specific commands via scsi-generic because we don't know how
to parse them.
If DMA is dele
This will be used for both scsi_block_new_request and the scsi-block
implementation of parse_cdb.
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-disk.c | 38 ++
1 file changed, 26 insertions(+), 12 deletions(-)
diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-d
The callback lets the bus provide the direction and transfer count
for passthrough commands, enabling passthrough of vendor-specific
commands.
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-bus.c | 3 +--
hw/scsi/scsi-disk.c| 14 ++
hw/scsi/scsi-generic.c | 7 +++
includ
These callbacks will let devices do their own request parsing, or
defer it to the bus. If the bus does not provide an implementation,
in turn, fall back to the default parsing routine.
Swap the first two arguments to scsi_req_parse, and rename it to
scsi_req_parse_cdb, for consistency.
Signed-of
Enable passthrough of vendor-specific commands.
Signed-off-by: Paolo Bonzini
---
hw/scsi/virtio-scsi.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index 0eb069a..2dd9255 100644
--- a/hw/scsi/virtio-scsi.c
+++ b/hw/s
On Tue, May 27, 2014 at 04:49:22PM +0800, Fam Zheng wrote:
> +if (!bs->backing_hd) {
> +memset(whole_grain, 0, skip_start_sector << BDRV_SECTOR_BITS);
> +memset(whole_grain + (skip_end_sector << BDRV_SECTOR_BITS), 0,
> + cluster_bytes - (skip_end_sector << BDRV_SE
On Wed, Jul 09, 2014 at 10:43:13AM +0800, Chunyan Liu wrote:
> Add nocow info in 'qemu-img info' output to show whether the file
> currently has NOCOW flag set or not.
>
> Signed-off-by: Chunyan Liu
> ---
> Changes:
> - update output info to "NOCOW flag: set"
>
> block/qapi.c | 25 +++
v3->v4:
drop all pretense of supporting bridges [me]
v2->v3:
fix tests/acpi-test-data/pc/DSDT [Peter]
track down "make check" failure, fix it [patch 4, me]
split patch 2 in two parts [mst]
do not make bsel_alloc global [mst]
include Igor's bridge pat
My version of IASL (from RHEL7) puts two newlines between the head comment
and the DefinitionBlock property. Kill all newlines after the comment,
so that normalize_asl works properly.
Signed-off-by: Paolo Bonzini
---
tests/bios-tables-test.c | 6 +-
1 file changed, 5 insertions(+), 1 deleti
This replaces the _PRT constant with a method that computes it.
The problem is that the DSDT+SSDT have grown from 2.0 to 2.1,
enough to cross the 8k barrier (we align the ACPI tables to 4k
before putting them in fw_cfg). This causes problems with
migration and the pc-i440fx-2.0 machine type.
The
This patch avoids that similar changes break QEMU again in the future.
QEMU will now hard-code 64k as the maximum ACPI table size, which
(despite being an order of magnitude smaller than 640k) should be enough
for everyone.
Reviewed-by: Laszlo Ersek
Tested-by: Igor Mammedov
Signed-off-by: Paolo
From: Igor Mammedov
Fixes migration regression from QEMU-1.7 to a newer QEMUs.
SSDT table size in QEMU-1.7 doesn't change regardless of
a number of PCI bridge devices present at startup.
However in QEMU-2.0 since addition of hotplug on PCI bridges,
each PCI bridge adds ~1875 bytes to SSDT table,
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In practice this is not the case, because the user
Support resizeable blobs: we allocate more memory than currently
available in the blob, which can later be filled in.
Signed-off-by: Michael S. Tsirkin
---
include/hw/loader.h | 14 +++--
include/hw/nvram/fw_cfg.h | 2 +-
hw/core/loader.c | 15 +
hw/nvram/fw_cfg.c
From: Igor Mammedov
Add API to mark memory region as extend-able on migration,
to allow migration code to load smaller RAMBlock into
a bigger one on destination QEMU instance.
This will allow to fix broken migration from QEMU 1.7/2.0 to
QEMU 2.1 due to ACPI tables size changes across 1.7/2.0/2.
This makes migration from older QEMU versions
more robust.
Signed-off-by: Michael S. Tsirkin
---
hw/core/loader.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hw/core/loader.c b/hw/core/loader.c
index ad6ec67..fc00a87 100644
--- a/hw/core/loader.c
+++ b/hw/core/loader.c
@@ -745,6 +
On Fri, Jul 18, 2014 at 09:33:42AM +, Wangkai (Kevin,C) wrote:
> fix vcpu long time io blocking on tap, when too many packets was delivered
> to the guest os via tap interface.
>
> --
> Signed-off-by: Wangkai
Thanks, applied to my net-next tree:
https://github.com/stefanha/qemu/commits/net-
> >
> > On 28.07.2014, at 16:16, David Hildenbrand wrote:
> >
> > >>
> > >> On 10.07.14 15:10, Christian Borntraeger wrote:
> > >>> From: David Hildenbrand
> > >>>
> > >>> If a cpu is stopped, it must never be allowed to run and no interrupt
> > >>> may wake it
> > >>> up. A cpu also has to
Use 'if' to make sure the real msb greater than the lsb. As the compiler may
not do this.
Signed-off-by: Dongxue Zhang
---
target-mips/translate.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index c381366..e2cce31 100644
--- a/ta
Free t0 and t1 in opcode OPC_DINSV.
Signed-off-by: Dongxue Zhang
---
target-mips/translate.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index d7b8c4d..c381366 100644
--- a/target-mips/translate.c
+++ b/target-mips/translate.c
@@ -1530
On Mon, Jul 28, 2014 at 05:34:16PM +0200, Paolo Bonzini wrote:
> This patch avoids that similar changes break QEMU again in the future.
> QEMU will now hard-code 64k as the maximum ACPI table size, which
> (despite being an order of magnitude smaller than 640k) should be enough
> for everyone.
Fam
On Sat, Jul 19, 2014 at 03:31:00PM +0800, melolinux wrote:
> 1. /usr/bin/qemu-system-x86_64 -machine accel=kvm -name
> a58970a2-10aa-4973-9261-7384b2f53221 -S -machine pc-0.14,accel=kvm,usb=off -m
> 4096 -smp 4,sockets=1,cores=4,threads=1 -uuid
> f3a2217f-ae5c-461b-a922-d37a3a98edc6 -no-user-con
Il 28/07/2014 17:59, Michael S. Tsirkin ha scritto:
> On Mon, Jul 28, 2014 at 05:34:16PM +0200, Paolo Bonzini wrote:
>> This patch avoids that similar changes break QEMU again in the future.
>> QEMU will now hard-code 64k as the maximum ACPI table size, which
>> (despite being an order of magnitude
On Wed, Jul 23, 2014 at 04:43:27AM -, selvakumar wrote:
> Public bug reported:
>
> [root@localhost pkgs]# qemu-img create virtualdisk.img 100M
> qemu-img: symbol lookup error: qemu-img: undefined symbol: glfs_discard_async
CCing Fedora qemu-kvm package maintainer.
Stefan
> [root@localhost p
1 - 100 of 155 matches
Mail list logo
