>>> On 5/28/2014 at 10:42 AM, in message <53854CFA.E55 : 102 : 21807>, Chun Yan
>>> Liu
wrote:
>
On 5/20/2014 at 05:11 AM, in message
> <20140519211122.GA2051@dorilex-lnv.MultilaserAP>, Leandro Dorileo
> wrote:
> > On Sun, May 18, 2014 at 09:02:45PM -0600, Chun Yan Liu wrote:
>>
On Mon, Jun 02, 2014 at 10:31:44PM +0200, Marcin Gibuła wrote:
> >+cpu_physical_memory_read(kvmclock_struct_pa, &time, sizeof(time));
> >+
> >+delta = migration_tsc - time.tsc_timestamp;
>
> Hi,
>
> when I was testing live storage migration with libvirt I found out
> that this patch can c
>>> On 5/29/2014 at 04:23 PM, in message <5386ee82.8040...@redhat.com>, Paolo
Bonzini wrote:
> Il 29/05/2014 05:23, Chunyan Liu ha scritto:
> > [support xen HVM direct kernel boot]
> > qemu side patch: if -kernel exists, calls xen_load_linux(), which
> > will read kernel/initrd and add a lin
>>> On 6/2/2014 at 11:24 PM, in message
<1401722652.30097.9.ca...@kazak.uk.xensource.com>, Ian Campbell
wrote:
> On Thu, 2014-05-29 at 11:23 +0800, Chunyan Liu wrote:
> > [support xen HVM direct kernel boot]
>
> What is this?
Just to indicate this is part of work to support xen HVM direct
On 05/21/2014 07:25 PM, Alexander Graf wrote:
>
> On 21.05.14 11:17, Peter Maydell wrote:
>> On 21 May 2014 08:51, Paolo Bonzini wrote:
>>> Il 21/05/2014 05:54, Alexey Kardashevskiy ha scritto:
>>>
Hi!
We recently discovered that not entire QEMU is GPL2-compatible, the fpu
emu
>>> On 6/3/2014 at 12:58 AM, in message
<20140602165836.gd5...@phenom.dumpdata.com>, Konrad Rzeszutek Wilk
wrote:
> On Mon, Jun 02, 2014 at 04:19:31PM +0100, Ian Campbell wrote:
> > On Fri, 2014-05-30 at 12:04 -0400, Konrad Rzeszutek Wilk wrote:
> > > On Thu, May 29, 2014 at 11:23:22AM +0800,
Add MemoryRegion and AddressSpace's for the master attachments of
the DMA engine. The MemoryRegions are exposed as links to be set by
the machine model (or whatever). At realize time, the memory regions
are used to construct the masterable AddressSpace's.
Could have been done simpler as just one A
Get rid of reliance on the global AddressSpace and implement the bus
hierachy properly.
This board design has two distinct masterable bus views.
* DDR - Used by DMA capable peripherals, contains only DDR memory.
* CPU - Used by CPU, contains everything.
CPU view is a superset of DDR view. Use ov
Rather than address_space_memory.
Needs a few random callsites with hardcoded address_space_memory to be
patched. Use first_cpu->as in these cases.
Signed-off-by: Peter Crosthwaite
---
Long term, cpu_physical_memory_rw and friends needs to be replaced.
exec.c | 5 +++--
hw/core/loade
Which is used to construct a per-CPU address space. The Address space
is constructed ASAP from the MemoryRegion property setter itself.
Signed-off-by: Peter Crosthwaite
---
include/qom/cpu.h | 1 +
qom/cpu.c | 30 ++
2 files changed, 31 insertions(+)
diff -
Just ignore this case. This is need for bus master device realize
when the machine model doesn't connect an attachment. Then machine
model may decide to not set a memory region for mastering yet the
device will attempt to create itself an address space come realize
time. Gracefully do nothing.
Sig
This will either create a new AS or return a pointer to an
already existing equivalent one. Both name and root mr must
match.
The motivation is to reuse address spaces as much as possible.
Its going to be quite common that bus masters out in device land
have pointers to the same memory region for
Rather than use the global singleton.
Signed-off-by: Peter Crosthwaite
---
exec.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/exec.c b/exec.c
index 32cc099..aa39f6c 100644
--- a/exec.c
+++ b/exec.c
@@ -1760,10 +1760,12 @@ static subpage_t *subpage_init(Add
As the QOM child. This gives Memory regions a canon path without
machines having to do it manually.
Unfortunately, there are no assurances against multiple memory
regions having the same name even when parented to the same owner.
We could munge names, but the canon paths will then get messy
and f
Parent the root MemoryRegions for Memory and IO to the machine. This
gives them a QOM path.
Signed-off-by: Peter Crosthwaite
---
exec.c | 4
1 file changed, 4 insertions(+)
diff --git a/exec.c b/exec.c
index 4e179a6..32cc099 100644
--- a/exec.c
+++ b/exec.c
@@ -1885,11 +1885,15 @@ static
This have 5 usages. Make it a bit more readable by using a local
variable.
Signed-off-by: Peter Crosthwaite
---
Theres three more usages of this in coming patches, that would push
the number of usages higher
hw/dma/xilinx_axidma.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
It's a constant based on a macro. Just use the macro in place.
Signed-off-by: Peter Crosthwaite
---
hw/microblaze/petalogix_ml605_mmu.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/hw/microblaze/petalogix_ml605_mmu.c
b/hw/microblaze/petalogix_ml605_mmu.c
index aea9c
Hi All,
This series implements Per-bus-Master Address spaces (PMA). It builds
on the merged components of Edgar's original series:
https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg01346.html
And my pending MemoryRegion QOMification:
https://lists.nongnu.org/archive/html/qemu-devel/2014-
> -Original Message-
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Monday, June 02, 2014 3:45 PM
> To: Gonglei (Arei)
> Cc: qemu-devel@nongnu.org; Luonengjun; Huangweidong (C); Huangpeng
> (Peter)
> Subject: Re: [PATCH 2/6] usb-ohci: add exit function
>
> Hi,
>
> > +static vo
> -Original Message-
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Monday, June 02, 2014 3:36 PM
> To: Gonglei (Arei)
> Cc: qemu-devel@nongnu.org; Luonengjun; Huangweidong (C); Huangpeng
> (Peter)
> Subject: Re: [PATCH 1/6] usb: add usb_bus_release function
>
> Hi,
>
> > +voi
> -Original Message-
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
> Sent: Tuesday, June 03, 2014 4:37 AM
> To: Chen, Tiejun
> Cc: anthony.per...@citrix.com; stefano.stabell...@eu.citrix.com;
> kelly.zyta...@amd.com; qemu-devel@nongnu.org;
> xen-de...@lists.xensource.com; peter.mayd..
On Tue, Jun 3, 2014 at 12:48 AM, Eric Blake wrote:
> On 06/02/2014 09:06 AM, Hitoshi Mitake wrote:
>> sheepdog dirver doesn't need to read data_vdi_id[] when a live
>
> s/dirver/driver/
Thanks for your comment. I'll send v2 later.
Thanks,
Hitoshi
>
>> snapshot is created.
>>
>
> --
> Eric Blake
Bring the memory map closer to a PowerMac3,1 model by removing unused
areas and adding the VGA and network cards after the macio to let the
latter be mapped from 0x8000 like on real hardware. (On real
hardware the graphics and network cards are on separate buses but we
don't model that yet.)
S
From: David Gibson
The only model so far supported for VFIO passthrough devices is the model
usually used on x86, where all of the guest's RAM is mapped into the
(host) IOMMU and there is no IOMMU visible in the guest.
This patch begins to relax this model, introducing the notion of a
VFIOAddres
On Mon, Jun 2, 2014 at 10:18 PM, Peter Maydell wrote:
> On 2 June 2014 05:17, Peter Crosthwaite wrote:
>> QOMify memory regions as an Object. The former init() and destroy()
>> routines become instance_init() and instance_finalize() resp.
>>
>> memory_region_init() is re-implemented to be:
>> obj
On Tue, Jun 3, 2014 at 12:26 AM, Peter Maydell wrote:
> On 2 June 2014 05:13, Peter Crosthwaite wrote:
>> This patch series QOMifies Memory regions. This is the Memory API
>> specific subset of patches forming part of the Memory/GPIO/Sysbus
>> QOMification.
>>
>> I think Paolo already has P1 enqe
From: David Gibson
This patch uses the new IOMMU notifiers to allow VFIO pass through devices
to work with guest side IOMMUs, as long as the host-side VFIO iommu has
sufficient capability and granularity to match the guest side. This works
by tracking all map and unmap operations on the guest IOM
From: Alexey Kardashevskiy
This reworks vfio_connect_container() and vfio_get_group() to have
common exit path at the end of the function bodies.
Signed-off-by: Alexey Kardashevskiy
Signed-off-by: Alex Williamson
---
hw/misc/vfio.c | 58 +++---
Dangit, I always manage to screw up something my qemu pull request. I'm
especially out of practice on this one.
Subject: VFIO pull request
Hopefully the rest is ok. Thanks,
Alex
On Mon, 2014-06-02 at 16:00 -0600, Alex Williamson wrote:
> The following changes since commit d7d3d6092cb7edc75dc4
On Mon, Jun 02, 2014 at 02:32:06PM +0200, Stefan Hajnoczi wrote:
> On Sat, May 31, 2014 at 10:39:40PM +0100, Hani Benhabiles wrote:
> > Signed-off-by: Hani Benhabiles
> > ---
> > include/block/nbd.h | 6 ++
> > nbd.c | 12 +++-
> > 2 files changed, 13 insertions(+), 5 d
This device is ridiculous. It has two MMIO BARs, BAR4 and BAR2. BAR4
hosts the MSI-X table, so oviously it would be too easy to access it
directly, instead it creates a window register in BAR2 that, among
other things, provides access to the MSI-X table. This means MSI-X
doesn't work in the gues
From: David Gibson
So far, VFIO has a notion of different logical DMA address spaces, but
only ever uses one (system memory). This patch extends this, creating
new VFIOAddressSpace objects as necessary, according to the AddressSpace
reported by the PCI subsystem for this device's DMAs.
This isn
From: Alexey Kardashevskiy
This adds macro to extend signed 64bit value to signed 128bit value.
Signed-off-by: Alexey Kardashevskiy
Reviewed-by: Paolo Bonzini
Signed-off-by: Alex Williamson
---
include/qemu/int128.h |5 +
1 file changed, 5 insertions(+)
diff --git a/include/qemu/int
From: Alexey Kardashevskiy
Upcoming VFIO on SPAPR PPC64 support will initialize the IOMMU
memory region with UINT64_MAX (2^64 bytes) size so int128_get64()
will assert.
The patch takes care of this check. The existing type1 IOMMU code
is not expected to map all 64 bits of RAM so the patch does n
From: David Gibson
At the moment, most AddressSpace objects last as long as the guest system
in practice, but that could well change in future. In addition, for VFIO
we will be introducing some private per-AdressSpace information, which must
be disposed of before the AddressSpace itself is destr
The following changes since commit d7d3d6092cb7edc75dc49fb90c86dd5425ab4805:
Merge remote-tracking branch 'remotes/afaerber/tags/qom-devices-for-peter'
into staging (2014-05-28 18:38:39 +0100)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-pci-for
On Mon, Jun 02, 2014 at 02:20:36PM +0200, Stefan Hajnoczi wrote:
> On Sun, Jun 01, 2014 at 12:53:35PM +0100, Hani Benhabiles wrote:
> > Signed-off-by: Hani Benhabiles
> > ---
> > util/readline.c | 9 +
> > 1 file changed, 9 insertions(+)
>
> Please only CC me on patches for areas of the
Am 02.06.2014 22:45, schrieb Paolo Bonzini:
Il 02/06/2014 21:32, Stefan Priebe ha scritto:
#0 0x7f69e421c43f in event_notifier_set (e=0x124) at
util/event_notifier-posix.c:97
#1 0x7f69e3e37afc in aio_notify (ctx=0x0) at async.c:246
#2 0x7f69e3e37697 in qemu_bh_schedule (bh=0x7f5d
Ping? qom-cpu is still broken and needs the fixes below.
Are there plans to include them and submit a pull request soon?
This one is also pending:
Message-ID: <20140529165514.gb13...@amt.cnet>
From: Marcelo Tosatti
Subject: [Qemu-devel] [qom/qom-cpu PATCH] i386: improve invtsc migration
Il 02/06/2014 21:32, Stefan Priebe ha scritto:
#0 0x7f69e421c43f in event_notifier_set (e=0x124) at
util/event_notifier-posix.c:97
#1 0x7f69e3e37afc in aio_notify (ctx=0x0) at async.c:246
#2 0x7f69e3e37697 in qemu_bh_schedule (bh=0x7f5dac217f60) at
async.c:128
#3 0x7f69e3e8bc
** Also affects: qemu
Importance: Undecided
Status: New
** Also affects: libvirt
Importance: Undecided
Status: New
** No longer affects: qemu
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Running a 3.14.4 x86-64 SMP guest kernel on qemu-2.0, with kvm enabled and
-cpu host on a 3.14.4 AMD Opteron host, I'm seeing a reliable kernel panic from
the guest shortly after boot. I think is happening in kvm_unlock_kick() in the
guest kernel paravirt_ops code:
divide error: [#1] PREEMPT
On Fri, May 30, 2014 at 04:59:28PM +0800, Tiejun Chen wrote:
> Implement that pci host bridge to specific to passthrough. Actually
> this just inherit the standard one.
>
> Signed-off-by: Tiejun Chen
Can this actually inherit TYPE_I440FX_PCI_DEVICE?
The parent is TYPE_PCI_DEVICE, but if it was T
+cpu_physical_memory_read(kvmclock_struct_pa, &time, sizeof(time));
+
+delta = migration_tsc - time.tsc_timestamp;
Hi,
when I was testing live storage migration with libvirt I found out that
this patch can cause virtual machine to hang when completing mirror job.
This is (probably) b
On 06/02/2014 02:20 PM, Marcelo Tosatti wrote:
> On Mon, Jun 02, 2014 at 01:31:29PM -0600, Eric Blake wrote:
>> On 06/02/2014 11:51 AM, mtosa...@redhat.com wrote:
>>> It is necessary to reset RTC interrupt reinjection backlog if
>>> guest time is synchronized via a different mechanism, such as
>>>
On Mon, Jun 02, 2014 at 01:31:29PM -0600, Eric Blake wrote:
> On 06/02/2014 11:51 AM, mtosa...@redhat.com wrote:
> > It is necessary to reset RTC interrupt reinjection backlog if
> > guest time is synchronized via a different mechanism, such as
> > QGA's guest-set-time command.
> >
> > Failing to
The exit code 63 (check not supported by image format) was not even
documented in the comment above the check command in the source code;
add it, as it does indeed seem useful.
Also, document all of check's exit codes in the manpage.
Signed-off-by: Max Reitz
Reported-by: Markus Armbruster
Revie
Il 02/06/2014 19:44, Dr. David Alan Gilbert ha scritto:
> If the version-based interface turns out to be not enough, we've done the
> work for nothing. In fact, we already know that it is not enough to solve
> 2.0->1.6 migration with -M pc-1.5.
Remind me, why doesn't it solve that?
(It would be
On Mon, Jun 02, 2014 at 01:13:18PM -0400, Gabriel L. Somlo wrote:
> Hi,
>
> On Mon, May 19, 2014 at 10:44:48PM +0300, Michael S. Tsirkin wrote:
> > On Mon, May 19, 2014 at 10:09:52AM -0400, Gabriel L. Somlo wrote:
> > > Changelog:
> > >
> > > new in v4:
> > > - slightly improved commit blurbs
>
On 02.06.2014 21:45, Eric Blake wrote:
On 06/02/2014 01:31 PM, Max Reitz wrote:
The exit code 63 (check not supported by image format) was not even
documented in the comment above the check command in the source code;
add it, as it does indeed seem useful.
Also, document all of check's exit cod
On 06/02/2014 01:31 PM, Max Reitz wrote:
> The exit code 63 (check not supported by image format) was not even
> documented in the comment above the check command in the source code;
> add it, as it does indeed seem useful.
>
> Also, document all of check's exit codes in the manpage.
>
> Signed-o
On 06/02/2014 01:20 PM, Marcelo Tosatti wrote:
> On Mon, Jun 02, 2014 at 01:05:50PM -0600, Eric Blake wrote:
>> On 06/02/2014 11:51 AM, mtosa...@redhat.com wrote:
>>> It is necessary to reset RTC interrupt backlog if guest time is
>>> synchronized via a different mechanism, such as QGA's guest-set-
Am 02.06.2014 15:40, schrieb Stefan Hajnoczi:
On Fri, May 30, 2014 at 04:10:39PM +0200, Stefan Priebe wrote:
even with
+From 271c0f68b4eae72691721243a1c37f46a3232d61 Mon Sep 17 00:00:00 2001
+From: Fam Zheng
+Date: Wed, 21 May 2014 10:42:13 +0800
+Subject: [PATCH] aio: Fix use-after-free in can
The exit code 63 (check not supported by image format) was not even
documented in the comment above the check command in the source code;
add it, as it does indeed seem useful.
Also, document all of check's exit codes in the manpage.
Signed-off-by: Max Reitz
Reported-by: Markus Armbruster
---
On 06/02/2014 11:51 AM, mtosa...@redhat.com wrote:
> It is necessary to reset RTC interrupt reinjection backlog if
> guest time is synchronized via a different mechanism, such as
> QGA's guest-set-time command.
>
> Failing to do so causes both corrections to be applied (summed),
> resulting in an
On Mon, Jun 02, 2014 at 01:05:50PM -0600, Eric Blake wrote:
> On 06/02/2014 11:51 AM, mtosa...@redhat.com wrote:
> > It is necessary to reset RTC interrupt backlog if guest time is
> > synchronized via a different mechanism, such as QGA's guest-set-time
> > command.
> >
> > Failing to do so causes
On Mon, 2014-06-02 at 15:03 -0400, Bandan Das wrote:
> Michael Tokarev writes:
>
> > 02.06.2014 17:30, Alex Williamson wrote:
> >> On Mon, 2014-06-02 at 14:32 +0400, Michael Tokarev wrote:
> >>> 01.06.2014 20:25, Alex Williamson wrote:
> The latest Nvidia driver (337.88) specifically checks
On Mon, 2014-06-02 at 15:09 -0400, Bandan Das wrote:
> Alex Williamson writes:
>
> > The latest Nvidia driver (337.88) specifically checks for KVM as the
> > hypervisor and reports Code 43 for the driver in a Windows guest when
> > found. Removing or changing the KVM signature is sufficient for
On Fri, May 30, 2014 at 03:47:51PM +0100, Leon Alrae wrote:
> From: Yongbok Kim
>
> Introduce MIPS32R6 Compact Branch instructions which do not have delay slot -
> they have forbidden slot instead. However, current implementation does not
> support forbidden slot yet.
>
> Signed-off-by: Yongbok
Alex Williamson writes:
> The latest Nvidia driver (337.88) specifically checks for KVM as the
> hypervisor and reports Code 43 for the driver in a Windows guest when
> found. Removing or changing the KVM signature is sufficient for the
> driver to load and work. This patch adds an option to ea
Michael Tokarev writes:
> 02.06.2014 17:30, Alex Williamson wrote:
>> On Mon, 2014-06-02 at 14:32 +0400, Michael Tokarev wrote:
>>> 01.06.2014 20:25, Alex Williamson wrote:
The latest Nvidia driver (337.88) specifically checks for KVM as the
hypervisor and reports Code 43 for the driver
On 06/02/2014 11:51 AM, mtosa...@redhat.com wrote:
> It is necessary to reset RTC interrupt backlog if guest time is
> synchronized via a different mechanism, such as QGA's guest-set-time
> command.
>
> Failing to do so causes both corrections to be applied (summed),
> resulting in an incorrect gu
On Mon, 2014-06-02 at 22:01 +0400, Michael Tokarev wrote:
> 02.06.2014 17:30, Alex Williamson wrote:
> > On Mon, 2014-06-02 at 14:32 +0400, Michael Tokarev wrote:
> >> 01.06.2014 20:25, Alex Williamson wrote:
> >>> The latest Nvidia driver (337.88) specifically checks for KVM as the
> >>> hyperviso
From: Markus Armbruster
Introduced in commit da557a. Spotted by Coverity.
Signed-off-by: Markus Armbruster
Reviewed-by: Benoit Canet
Signed-off-by: Kevin Wolf
---
block.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block.c b/block.c
index a517d72..310ea89 100644
--- a/block.c
+++ b/
Signed-off-by: Gerd Hoffmann
---
include/ui/console.h | 1 +
ui/console.c | 24
2 files changed, 25 insertions(+)
diff --git a/include/ui/console.h b/include/ui/console.h
index b513e20..4ad16c9 100644
--- a/include/ui/console.h
+++ b/include/ui/console.h
@@ -82,
On 06/02/2014 04:50 AM, Gerd Hoffmann wrote:
> @@ -1996,6 +1997,9 @@ if test "$gtk" != "no"; then
> gtk_libs=`$pkg_config --libs $gtkpackage`
> libs_softmmu="$gtk_libs $libs_softmmu"
> gtk="yes"
> +if $pkg_config --exists "$gtkx11package >= $gtkversion"; then
> +
On 06/02/2014 09:06 AM, Hitoshi Mitake wrote:
> sheepdog dirver doesn't need to read data_vdi_id[] when a live
s/dirver/driver/
> snapshot is created.
>
--
Eric Blake eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP
The Friday 30 May 2014 à 20:13:42 (+0200), Markus Armbruster wrote :
> We got a merry mix of -1 and -errno here.
>
> Signed-off-by: Markus Armbruster
> Reviewed-by: Eric Blake
> ---
> block/raw-posix.c | 28 ++--
> 1 file changed, 22 insertions(+), 6 deletions(-)
>
> di
On 06/02/2014 06:31 PM, Kevin Wolf wrote:
Am 02.06.2014 um 17:04 hat Chrysostomos Nanakos geschrieben:
Hi,
On 06/02/2014 05:30 PM, Eric Blake wrote:
On 06/02/2014 08:15 AM, Chrysostomos Nanakos wrote:
VM Image on Archipelago volume is specified like this:
file=archipelago:[/mport=[:vport=]]
On Mon, Jun 02, 2014 at 02:58:05PM +0200, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > Signed-off-by: Eduardo Habkost
> > ---
> > Cc: Anthony Liguori
> > Cc: Amos Kong
> > ---
> > backends/rng-egd.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/backends/rng-egd.c
On Fri, 30 May 2014, Tiejun Chen wrote:
> basic gfx passthrough support:
> - add a vga type for gfx passthrough
> - retrieve VGA bios from sysfs, then load it to guest at 0xC
> - register/unregister legacy VGA I/O ports and MMIOs for passthrough GFX
>
> The original patch is from Weidong Han
02.06.2014 17:30, Alex Williamson wrote:
> On Mon, 2014-06-02 at 14:32 +0400, Michael Tokarev wrote:
>> 01.06.2014 20:25, Alex Williamson wrote:
>>> The latest Nvidia driver (337.88) specifically checks for KVM as the
>>> hypervisor and reports Code 43 for the driver in a Windows guest when
>>> fou
It is necessary to reset RTC interrupt backlog if guest time is
synchronized via a different mechanism, such as QGA's guest-set-time
command.
Failing to do so causes both corrections to be applied (summed),
resulting in an incorrect guest time.
---
changelog:
v3:
- add object_property_add_ali
Add a link to rtc under /machine providing a stable
location for management apps to query "date" field.
{"execute":"qom-get","arguments":{"path":"/machine/rtc","property":"date"} }
Suggested by Paolo Bonzini.
Signed-off-by: Marcelo Tosatti
Index: qemu/hw/timer/mc146818rtc.c
==
Allowing addition of a link without keeping pointer-to-pointer.
Signed-off-by: Marcelo Tosatti
Index: qemu/include/qom/object.h
===
--- qemu.orig/include/qom/object.h
+++ qemu/include/qom/object.h
@@ -1073,6 +1073,19 @@ typedef enum
It is necessary to reset RTC interrupt reinjection backlog if
guest time is synchronized via a different mechanism, such as
QGA's guest-set-time command.
Failing to do so causes both corrections to be applied (summed),
resulting in an incorrect guest time.
Signed-off-by: Marcelo Tosatti
Index:
This enables the saving and restoring of machine state by including the
current program state (*psr) and xregs. The save_state_to_spsr hides the
details of if the processor is in 32 or 64 bit mode at the time.
---
v2 (ajb)
- use common state save functions
- re-base to latest origin/master
Hi,
This started with a hack-patch Peter had written to get migration
working for aarch64 system images. It was noted that cpu.h was
starting to proliferate program state functions. This series attempts
to fix that by:
- creating a "universal" save/restore_to/from_spsr function
- using that f
This adds a universal program state save and restore function. This is
intended to simplify the migration serialisation functionality and avoid
special casing depending on the mode of the CPU at serialisation time.
---
WIP notes:
- From this I'll look at
- cpsr_read/cpsr_write
- p
so that management could detect via QOM interface if device was
hotplugged
Signed-off-by: Igor Mammedov
Acked-by: Peter Crosthwaite
---
v2:
- fix typo in commit message (afaerber)
---
hw/core/qdev.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/hw/co
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> Il 02/06/2014 18:40, Dr. David Alan Gilbert ha scritto:
> >
> >So putting this in now, and getting it into libvirt means everyone has
> >the info.
> >>>
> >>> It also means we have a higher risk of getting it wrong, and having to do
> >
On Fri, 30 May 2014, Tiejun Chen wrote:
> ISA bridge is needed since Intel gfx drive will probe it instead
> of Dev31:Fun0 to make graphics device passthrough work easy for VMM, that
> only need to expose ISA bridge to let driver know the real hardware
> underneath.
>
> The original patch is from
On 06/02/2014 09:49 AM, Chrysostomos Nanakos wrote:
I still think that there is no need to burden the code with this
shorthand...
>>> If everyone agrees I can totally remove that part.
>> I don't think it's a bad idea to provide a shortcut for human users. The
>> important point is just
Il 02/06/2014 18:40, Dr. David Alan Gilbert ha scritto:
> >
> >So putting this in now, and getting it into libvirt means everyone has the
info.
>
> It also means we have a higher risk of getting it wrong, and having to do
> the work twice.
That's why all this is does is provide the interface;
Adds get_hotplug_handler() method to machine, and
makes bus-less device to use it during hotplug
as a means to discover hotplug handler controller.
Returned controller is used to permorm a hotplug
action.
Signed-off-by: Igor Mammedov
Acked-by: Peter Crosthwaite
---
hw/core/qdev.c | 13 ++
On Fri, 30 May 2014, Tiejun Chen wrote:
> Some registers of Intel IGD are mapped in host bridge, so it needs to
> passthrough these registers of physical host bridge to guest because
> emulated host bridge in guest doesn't have these mappings.
>
> The original patch is from Weidong Han < weidong.h
On 05/31/2014 05:50 AM, Benoît Canet wrote:
> Signed-off-by: Benoit Canet
> ---
> qapi-schema.json | 15 ---
> qapi/block-core.json | 15 +++
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
> + } }
> +
>
Similar comments as in 2/72 about trailing blank line
The latest Nvidia driver (337.88) specifically checks for KVM as the
hypervisor and reports Code 43 for the driver in a Windows guest when
found. Removing or changing the KVM signature is sufficient for the
driver to load and work. This patch adds an option to easily allow
the KVM hypervisor sign
And use the new machinery to to save and restore program state. The old
cpsr_write function did some special handling for mode switches which
has been moved into the helper function.
diff --git a/linux-user/main.c b/linux-user/main.c
index 5d9d5f7..e594741 100644
--- a/linux-user/main.c
+++ b/linu
Hi,
Documentation update for multiseat setup.
cheers,
Gerd
Gerd Hoffmann (3):
docs/multiseat.txt: use autoseat
docs/multiseat.txt: gtk joined the party
docs/multiseat.txt: add note about spice
docs/multiseat.txt | 78 --
1 file chan
We have a number of program state saving functions (pstate, cpsr, xpsr)
which are dependant on the mode the CPU is in. This commit adds a little
documentation to each function and asserts to defend against incorrect
use.
diff --git a/target-arm/cpu.h b/target-arm/cpu.h
index 8d04385..5e6df38 10064
Hi,
On Mon, May 19, 2014 at 10:44:48PM +0300, Michael S. Tsirkin wrote:
> On Mon, May 19, 2014 at 10:09:52AM -0400, Gabriel L. Somlo wrote:
> > Changelog:
> >
> > new in v4:
> > - slightly improved commit blurbs
> >
> > v3:
> > - endian-ness fix (1/3) now correctly handles cpuid version and
Signed-off-by: Gerd Hoffmann
---
ui/sdl2.c | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/ui/sdl2.c b/ui/sdl2.c
index 0e884f9..749fa89 100644
--- a/ui/sdl2.c
+++ b/ui/sdl2.c
@@ -49,6 +49,7 @@ static struct sdl2_state {
int idx;
int last_v
Hi,
Here comes the seabios update from -rc1 to -final.
please pull,
Gerd
The following changes since commit 9bb931802e6ab5ab6947e3cb9cea934fc0724274:
Revert "bsd-user: replace fprintf(stderr, ...) with error_report()"
(2014-06-02 13:26:59 +0100)
are available in the git repository at:
Use the unified save_state_to_spsr. I've also updated the interrupt
helpers to restore via the restore_state_from_spsr() functions. In the
aarch32 case this also needs to call switch_mode() to do the appropriate
fiddling.
diff --git a/linux-user/elfload.c b/linux-user/elfload.c
index 995f999..a93a
On Mon, Jun 02, 2014 at 04:19:31PM +0100, Ian Campbell wrote:
> On Fri, 2014-05-30 at 12:04 -0400, Konrad Rzeszutek Wilk wrote:
> > On Thu, May 29, 2014 at 11:23:22AM +0800, Chunyan Liu wrote:
> > > Following previous discussion:
> > > https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg03843.
Benoît Canet writes:
> The Friday 30 May 2014 à 20:13:51 (+0200), Markus Armbruster wrote :
>> bdrv_get_geometry() hides errors. Use bdrv_nb_sectors() or
>> bdrv_getlength() instead where that's obviously inappropriate.
>>
>> Signed-off-by: Markus Armbruster
>> Reviewed-by: Eric Blake
>> Revi
Benoît Canet writes:
> The Friday 30 May 2014 à 20:13:48 (+0200), Markus Armbruster wrote :
>> Instead of bdrv_getlength().
>>
>> Aside: a few of these callers don't handle errors. I didn't
>> investigate whether they should.
>>
>> Signed-off-by: Markus Armbruster
>> Reviewed-by: Eric Blake
* Paolo Bonzini (pbonz...@redhat.com) wrote:
> Il 02/06/2014 15:50, Dr. David Alan Gilbert ha scritto:
> >However, it gets trickier since the destination libvirt has to know to send
> >the version information to the source; so we can only use this trick between
> >versions where the libvirt on both
Did you mean to keep the commented-out asserts in xpsr_read/write?
On 2 June 2014 11:21, Alex Bennée wrote:
> We have a number of program state saving functions (pstate, cpsr, xpsr)
> which are dependant on the mode the CPU is in. This commit adds a little
> documentation to each function and a
1 - 100 of 334 matches
Mail list logo
