-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-16 22:55, Mike Frysinger wrote:
> On Sunday 16 September 2012 16:33:15 Stefan Weil wrote:
>> Am 16.09.2012 22:11, schrieb Mike Frysinger:
>>> +libcacard/vscclient +a.out* +.gdb_history +core +gmon.out
>>> +*.diff +*.patch +*.rej
>>
>> IMHO
Il 16/09/2012 16:40, Anthony Liguori ha scritto:
> It's good to put includes in a single direction such that you can do
> -Iinclude and then:
>
> #include "qemu/foo.h"
>
> Which is better than:
>
> #include "foo.h"
>
> Because the later can create confusion/conflict with system headers
> wherea
Il 16/09/2012 16:44, Anthony Liguori ha scritto:
> Thanks for doing this! I'm of the opinion that something is better than
> nothing here so I'll resist the urge to argue why blue is the best color
> for the shed.
>
> But one concern I have: this will be a big source of rebasing. Perhaps
> we ca
Il 16/09/2012 22:03, Mike Frysinger ha scritto:
>>> > > +ifeq ($(findstring clean,$(MAKECMDGOALS)),)
>> >
>> > Please use instead:
>> >
>> > ifneq ($(filter-out %clean,$(MAKECMDGOALS)),)
>> >
>> > so that "make clean all" still gives error.
> that breaks `make` though. or rather, `make` no long
Am 16.09.2012 13:41, schrieb Michael Tokarev:
> The text describing `create' qemu-img subcommand refers to backing_file,
> but it is not mentioned anywhere in the syntax for this subcommand.
>
> Signed-off-by: Michael Tokarev
No, -b is deprecated, you should be using -o backing_file=...
What de
Am 16.09.2012 12:13, schrieb Peter Lieven:
> Hi,
>
> when trying to block migrate a VM from one node to another, the source
> VM crashed with the following assertion:
> block.c:3829: bdrv_set_in_use: Assertion `bs->in_use != in_use' failed.
>
> Is this sth already addresses/known?
Not that I'm
Il 16/09/2012 22:07, Mike Frysinger ha scritto:
> There's no reason to require configure to run before running a clean
> target, so check MAKECMDGOALS before.
>
> Signed-off-by: Mike Frysinger
> ---
> v2
> - handle edge cases
>
> Makefile |4
> 1 file changed, 4 insertions(+)
>
Misc microblaze patches.
Chris Wulff (1):
xilinx_timer: Fix a compile error if debug enabled
Peter A. G. Crosthwaite (5):
xilinx_timer: Removed comma in device name
xilinx_timer: Send dbg msgs to stderr not stdout
xilinx_timer: Fixed "frequency" prop name
xilinx.h: Error check when sett
Fixes an error in a61e4b07a30c062260d2d01771773f14820d1eb7
Signed-off-by: Peter A. G. Crosthwaite
---
hw/xilinx.h |2 +-
hw/xilinx_timer.c |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/xilinx.h b/hw/xilinx.h
index 556c5aa..df06a00 100644
--- a/hw/xilinx
Signed-off-by: Peter A. G. Crosthwaite
---
hw/xilinx_timer.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/xilinx_timer.c b/hw/xilinx_timer.c
index 053ba02..c02e6ca 100644
--- a/hw/xilinx_timer.c
+++ b/hw/xilinx_timer.c
@@ -119,7 +119,7 @@ timer_read(void *opa
Assert that the ethernet and dma controller are sucessfully linked to their
peers.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/xilinx.h | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/hw/xilinx.h b/hw/xilinx.h
index 45a6bdc..4d29265 100644
--- a/hw/xilinx.h
++
These names were incorrect. Fixed to match to actual link names
Signed-off-by: Peter A. G. Crosthwaite
---
hw/xilinx.h |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/hw/xilinx.h b/hw/xilinx.h
index 4d29265..6449bd4 100644
--- a/hw/xilinx.h
+++ b/hw/xilinx.h
@@ -63,
The "frequency" qdev prop matches the "clock-frequency" property in Xilinx EDK.
Renamed "frequency" -> "clock-frequency" accordingly.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/xilinx.h |2 +-
hw/xilinx_timer.c |3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git
In response to Chris Wulff series which add FDT driver machine generation for
microblaze, heres the current version of the system maintained out of tree at
Xilinx.
Looking to collaborate with Chris (or anyone else out there) on how we can
converge our implementations.
Major outstanding issues:
Signed-off-by: Peter A. G. Crosthwaite
---
device_tree.c | 10 +-
device_tree.h |2 +-
hw/arm_boot.c |4 ++--
3 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/device_tree.c b/device_tree.c
index d7a9b6b..92a383e 100644
--- a/device_tree.c
+++ b/device_tree.c
@@ -19
Hi,
On 09/15/2012 06:27 PM, Jan Kiszka wrote:
From: Jan Kiszka
This follows the logic of host-linux: If a 2.0 device has no ISO
endpoint and no interrupt endpoint with a packet size > 64, we can
attach it also to an 1.1 host controller. In case the redir server does
not report endpoint sizes,
Signed-off-by: Laszlo Ersek
---
Build tested.
console.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/console.c b/console.c
index c1ed5e0..67080f4 100644
--- a/console.c
+++ b/console.c
@@ -938,8 +938,11 @@ static void console_putchar(TextConsole *s, int ch)
First revision of fdt generic platform for xilinx microblaze platforms.
Adds machine model "microblaze-fdt" which can be used along with the --hw-dtb
option to lauch dts driven machine models for microblaze platforms.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/microblaze/Makefile.objs |1
First revision of fdt generic infrastructure. These modules allow
for fdt generic machine models, which create machines to match a device
tree specification.
Signed-off-by: Peter A. G. Crosthwaite
---
default-configs/microblaze-softmmu.mak |1 +
default-configs/microblazeel-softmmu.mak |
getprop currently return a pointer into the device tree itself. These pointers
will be corrupted if the device tree is written to in anyway. To make getprop()
safe, duplicate the property so that the value doesnt change over the lifetime
of the returned pointer.
Signed-off-by: Peter A. G. Crosthwa
Il 15/09/2012 03:13, Ronnie Sahlberg ha scritto:
> QEMU as far as I know only reports LUN numbers using the modes that
> are described in SAM4.
> As such, since all LUN numbers generated by the SCSI emulation in QEMU
> follow SAM4, we should set the HiSup bit in the standard INQUIRY data
> to indic
On 2012-09-17 11:08, Hans de Goede wrote:
> Hi,
>
> On 09/15/2012 06:27 PM, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> This follows the logic of host-linux: If a 2.0 device has no ISO
>> endpoint and no interrupt endpoint with a packet size > 64, we can
>> attach it also to an 1.1 host controlle
Added fdt generic platform support. Note that this does not add the fdt init
handler to the table of registered models as this needs to be handled in a
platform dependent way (due to target endianness issues). Fdt generic machine
models are required to register this device should it be supported.
Extended the wrapper interface (around libfdt) for device tree. Node Property
getters have been added (qemu_devtree_getprop*) as well as helpers to search/
navigate the nodes of a FDT blob.
Signed-off-by: Peter A. G. Crosthwaite
---
device_tree.c | 158 ++
fdt generic platform support for 16550 uarts.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/fdt_generic_devices.c | 39 +--
1 files changed, 37 insertions(+), 2 deletions(-)
diff --git a/hw/fdt_generic_devices.c b/hw/fdt_generic_devices.c
index 91b3c5b..690
Add a function co_queue_enter_next() which will immediately transfer
control to the coroutine at the head of a co queue. This can be used for
implementing simple work queues where the manager of a co-queue only
needs to enter queued routines one at a time.
Signed-off-by: Peter A. G. Crosthwaite
-
From: Chris Wulff
There was a missing include of qemu-log and a variable name in a printf was out
of date.
Signed-off-by: Chris Wulff
Signed-off-by: Peter A. G. Crosthwaite
---
hw/xilinx_timer.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/hw/xilinx_timer.c b/hw/
On Mon, Sep 17, 2012 at 1:08 AM, Aurelien Jarno wrote:
> Now that the setcond TCG op is available, it's possible to replace
> shl and shr helpers by TCG code. The code generated by TCG is slightly
> longer than the code generated by GCC for the helper but is still worth
> it as this avoid all the
If the inherit flag is set, and the specified property is not found, then search
the parents for it as well.
Signed-off-by: Peter A. G. Crosthwaite
---
device_tree.c | 11 ---
device_tree.h |4 ++--
hw/arm_boot.c |6 --
3 files changed, 14 insertions(+), 7 deletions(-)
dif
Rather than exit(1) on fail return an Error*. Clients can then handle errors as
they wish.
Signed-off-by: Peter A. G. Crosthwaite
---
device_tree.c | 25 ++---
device_tree.h |9 +++--
hw/arm_boot.c |8 ++--
3 files changed, 31 insertions(+), 11 deletions(-)
On 17 September 2012 10:30, Laurent Desnogues
wrote:
> On Mon, Sep 17, 2012 at 1:08 AM, Aurelien Jarno wrote:
>> +#define GEN_SHIFT(name)\
>> +static void gen_##name(TCGv dest, TCGv t0, TCGv t1)\
>> +{ \
>> +
Il 17/09/2012 11:02, Peter A. G. Crosthwaite ha scritto:
> First revision of fdt generic infrastructure. These modules allow
> for fdt generic machine models, which create machines to match a device
> tree specification.
Ok, so here is the famous coroutine-based FDT generation. :)
It does look p
Signed-off-by: Evgeny Voevodin
---
hw/virtio-balloon.c | 42 ++
hw/virtio-balloon.h |9 +
2 files changed, 51 insertions(+)
diff --git a/hw/virtio-balloon.c b/hw/virtio-balloon.c
index dd1a650..d6fe2aa 100644
--- a/hw/virtio-balloon.c
+++ b/h
On Mon, Sep 17, 2012 at 7:48 PM, Paolo Bonzini wrote:
> Il 17/09/2012 11:02, Peter A. G. Crosthwaite ha scritto:
>> First revision of fdt generic infrastructure. These modules allow
>> for fdt generic machine models, which create machines to match a device
>> tree specification.
>
> Ok, so here is
Dear Michael Tokarev,
> On 17.09.2012 00:36, Marek Vasut wrote:
> >> Dear Michael Tokarev,
> >
> > Bump? Did this lead anywhere? Do you need updated patch?
>
> This didn't lead to anywhere. I just pointed out that we
> have similar issue and somewhat similar change, and it
> weren't sufficient.
From: Peter Maydell
The MMIO virtio transport spec allows the guest to tell the host how
large the queue size is. Add virtio_queue_set_num() function which
implements this in the QEMU common virtio support code.
Signed-off-by: Peter Maydell
Signed-off-by: Evgeny Voevodin
---
hw/virtio.c |
Signed-off-by: Evgeny Voevodin
---
hw/Makefile.objs |1 +
hw/virtio-transport.c | 147 +
hw/virtio-transport.h | 74 +
3 files changed, 222 insertions(+)
create mode 100644 hw/virtio-transport.c
create mode 1006
From: Peter Maydell
Support virtio transports which can specify the vring alignment
(ie where the guest communicates this to the host) by providing
a new virtio_queue_set_align() function. (The default alignment
remains as before.)
FIXME save/load support for this new field!
Signed-off-by: Pete
From: Peter Maydell
Add support for the generic MMIO based virtio transport.
This patch is a modyfied patch of
Peter Maydell . Changes are to have
virtio-mmio bridge device which provides virtio-mmio bus. To this bus
virtio-mmio-transport device is connected and in turn provides
virtio-transport
Signed-off-by: Evgeny Voevodin
---
hw/virtio-serial-bus.c | 44
hw/virtio-serial.h | 11 +++
2 files changed, 55 insertions(+)
diff --git a/hw/virtio-serial-bus.c b/hw/virtio-serial-bus.c
index 82073f5..699a485 100644
--- a/hw/virtio-s
Signed-off-by: Evgeny Voevodin
---
hw/virtio-net.c | 59 +++
hw/virtio-net.h | 16 +++
2 files changed, 75 insertions(+)
diff --git a/hw/virtio-net.c b/hw/virtio-net.c
index b1998b2..b7cfb1c 100644
--- a/hw/virtio-net.c
+++ b/hw
This commit adds VirtIOPCI device implementation which is temporary
held in virtio-pci-new.c file. We need this file until virtio-xxx-pci
devices in hw/virtio-pci.c are not implemented in the way that they
just create virtio-pci and virtio-xxx devices during initialization.
Signed-off-by: Evgeny V
Signed-off-by: Evgeny Voevodin
---
hw/virtio-blk.c | 65 +++
hw/virtio-blk.h | 15 +
2 files changed, 80 insertions(+)
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index 6f6d172..0a23352 100644
--- a/hw/virtio-blk.c
+++ b/hw/v
Previous RFC you can find at
http://lists.gnu.org/archive/html/qemu-devel/2012-04/msg03665.html
Yes, long time ago...
Since I'm not sure when I'll be able to continue on this,
I'm publishing this work as is.
In this patchset I tried to split virtio-xxx-pci devices into
virtio-pci + virtio-xxx (bl
NB: This is for test purposes only.
Signed-off-by: Evgeny Voevodin
---
hw/exynos4210.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/hw/exynos4210.c b/hw/exynos4210.c
index 00d4db8..70fcdd6 100644
--- a/hw/exynos4210.c
+++ b/hw/exynos4210.c
@@ -26,6 +26,7 @@
#include "sys
We need to use this function to load rom for virtio-net backend.
Signed-off-by: Evgeny Voevodin
---
hw/pci.c |3 +--
hw/pci.h |2 ++
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index f855cf3..bba69ef 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -77,7 +77
Virtio back-end devices can be plugged into both transports:
VIRTIO_PCI and VIRTIO_MMIO. In order to choose the desired
transport we have a property "transport" in every back-end
state struct. By specifying -device virtio-blk-pci user chooses
VIRTIO_PCI transport and "transport" property is set aut
According to the documentation drivers using this device should read
FB_SIZE before enabling the device to know what memory to map. This
would not work if we return 0 before enabled.
Signed-off-by: BALATON Zoltan
---
hw/vmware_vga.c | 13 -
1 file changed, 8 insertions(+), 5 delet
Postpone stopping the dirty log to the point where the command fifo is
configured to allow drivers which don't use the fifo to work too.
(Without this the picture rendered into the vram never got to the
screen and the DIRECT_VRAM option meant to support this case was
removed a year ago.)
Signed-o
Removed info from vmsvga_state that is available from elsewhere and
thus was duplicated here unnecessarily. Also includes some coding
style fixes suggested by checkpatch.pl.
Signed-off-by: BALATON Zoltan
---
console.h | 20 ++
hw/vmware_vga.c | 196 +++--
Laszlo Ersek writes:
> Signed-off-by: Laszlo Ersek
> ---
> Build tested.
> console.c |7 +--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/console.c b/console.c
> index c1ed5e0..67080f4 100644
> --- a/console.c
> +++ b/console.c
> @@ -938,8 +938,11 @@ static void
On Sat, Sep 15, 2012 at 04:55:24PM +0100, Richard Davies wrote:
> Hi Rik, Mel and Shaohua,
>
> Thank you for your latest patches. I attach my latest perf report for a slow
> boot with all of these applied.
>
Thanks for testing.
> Mel asked for timings of the slow boots. It's very hard to give a
Il 17/09/2012 12:00, Evgeny Voevodin ha scritto:
> Virtio back-end devices can be plugged into both transports:
> VIRTIO_PCI and VIRTIO_MMIO. In order to choose the desired
> transport we have a property "transport" in every back-end
> state struct. By specifying -device virtio-blk-pci user chooses
> > However, as things stand there is nothing (I think) that really requires
> > coroutines. A simple 2-pass initialization would do, with links and
> > irqs connected on the second pass.
>
> I'm just trying to be a little more general. For more complex setups
> we may in the future want to resol
Paolo Bonzini writes:
> Il 16/09/2012 16:44, Anthony Liguori ha scritto:
>> Thanks for doing this! I'm of the opinion that something is better than
>> nothing here so I'll resist the urge to argue why blue is the best color
>> for the shed.
>>
>> But one concern I have: this will be a big sourc
On 5 September 2012 20:07, Francesco Lavra wrote:
> Documentation at
> http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503c/CHDEFDJF.html
> says that the entire first 512 MB can be mapped to either SMC (which is
> the default) or AXI, so if AXI is selected neither of the 2 flash banks
> is vi
On 15 September 2012 17:41, Blue Swirl wrote:
> On Sat, Sep 15, 2012 at 8:57 AM, Daniel Forsgren
> wrote:
>> 1) What is considered to be part of the "core" and what is
>> considered to be a device external to the core? To me, it looks
>> like co-processor functionality in general is considered to
On Mon, Sep 17, 2012 at 11:43 AM, Peter Maydell
wrote:
> On 17 September 2012 10:30, Laurent Desnogues
> wrote:
>> On Mon, Sep 17, 2012 at 1:08 AM, Aurelien Jarno wrote:
>>> +#define GEN_SHIFT(name)\
>>> +static void gen_##name(TCGv dest, TCGv t0, TCGv t1)\
>>
Also known as Paravirtualization CPUIDs.
This is primarily done so that the guest will think it is running
under vmware when hypervisor-vendor=vmware is specified as a
property of a cpu.
This depends on:
http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg01400.html
As far as I know it is
Also known as Paravirtualization vendor.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Al
This is EBX, ECX, EDX data.
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
VMware documention on
forgot to delete the backup versions. :(
-Don
On 09/17/12 09:39, Don Slutz wrote:
*** BLURB HERE ***
Don Slutz (17):
target-i386: Allow tsc-frequency to be larger then 2.147G
target-i386: Add missing kvm bits.
target-i386: Add Hypervisor level.
target-i386: Add cpu object access
On 09/15/2012 11:55 AM, Richard Davies wrote:
Hi Rik, Mel and Shaohua,
Thank you for your latest patches. I attach my latest perf report for a slow
boot with all of these applied.
Mel asked for timings of the slow boots. It's very hard to give anything
useful here! A normal boot would be a minu
On 17 September 2012 14:36, Laurent Desnogues
wrote:
> On Mon, Sep 17, 2012 at 11:43 AM, Peter Maydell
> wrote:
>> The TCG shift operations are undefined behaviour (not merely
>> undefined result) if the shift is >= 32, so we must avoid
>> doing that even if we're going to throw away the answer.
On 09/17/12 09:49, Don Slutz wrote:
forgot to delete the backup versions. :(
-Don
On 09/17/12 09:39, Don Slutz wrote:
Here is the planned cover letter:
From 7c0a80d8e870da981786b7235d3a968024c89abb Mon Sep 17 00:00:00 2001
In-Reply-To: <1346354435-21685-1-git-send-email-...@cloudswitch.com>
Send it to stderr before free of the details.
Signed-off-by: Don Slutz
---
v2: Change __FUNCTION__ to __func__
target-i386/cpu.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 57c064f..760cca4 100644
--- a/target-i386/cpu.c
+
Resend with new id so the backup files are not included.
Also known as Paravirtualization CPUIDs.
This is primarily done so that the guest will think it is running
under vmware when hypervisor-vendor=vmware is specified as a
property of a cpu.
This depends on:
http://lists.gnu.org/archive/html
Also known as Paravirtualization vendor.
This is EBX, ECX, EDX data for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel chang
Signed-off-by: Don Slutz
---
target-i386/cpu.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 5afb188..1b3a472 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1842,9 +1842,9 @@ void cpu_x86_cpuid(CPUX86State *en
On Mon, Sep 17, 2012 at 09:50:08AM -0400, Rik van Riel wrote:
> On 09/15/2012 11:55 AM, Richard Davies wrote:
> >Hi Rik, Mel and Shaohua,
> >
> >Thank you for your latest patches. I attach my latest perf report for a slow
> >boot with all of these applied.
> >
> >Mel asked for timings of the slow b
Signed-off-by: Don Slutz
---
target-i386/cpu.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index 47bc00c..a2d3588 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -799,6 +799,10 @@ typedef struct CPUX86State {
uin
Signed-off-by: Don Slutz
---
target-i386/kvm.c | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index b8789f2..17c72bc 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -454,6 +454,25 @@ int kvm_arch_init_vcp
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index bfaee02..89a45b5 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1975,6 +1975,17 @@ void cpu_x86_cpuid(CPUX86St
These are modeled after x86_cpuid_get_xlevel and x86_cpuid_set_xlevel.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 5f9866a..0e4a18d 100644
--- a/tar
Also known as Paravirtualization level or maximim cpuid function present in
this leaf.
This is just the EAX value for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware
This is just the EAX value.
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
VMware documention on
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 36 +++-
target-i386/cpu.h | 12
2 files changed, 47 insertions(+), 1 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 1b3a472..9ac3076 100644
--- a/target-i386/cpu.c
+++ b/targ
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Als
This was taken from:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/22643
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 34d2291..bfaee0
Also known as Paravirtualization vendor.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Al
Hi,
On 09/17/2012 11:18 AM, Jan Kiszka wrote:
On 2012-09-17 11:08, Hans de Goede wrote:
Although not pretty I'm ok with this, since I actually want to add
similar code to allow usb-3 (superspeed) devices like a usb-3 usb-stick
to work with ehci or uhci controllers :)
Great, that would hav
These are modeled after x86_cpuid_set_vendor and x86_cpuid_get_vendor.
Since kvm's vendor is shorter, the test for correct size is removed and zero
padding is added.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 44
1 files changed, 44 insertion
Hi
Please send in any agenda items you are interested in covering.
Thanks, Juan.
Signed-off-by: Don Slutz
---
target-i386/kvm.c | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index b8789f2..17c72bc 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -454,6 +454,25 @@ int kvm_arch_init_vcp
On 09/05/12 16:24, Don Slutz wrote:
On 08/31/12 13:27, Jan Kiszka wrote:
On 2012-08-31 19:20, Don Slutz wrote:
This is known is linux as VMWARE_PORT_CMD_GETHZ.
Signed-off-by: Don Slutz
---
hw/vmport.c | 23 ++-
1 files changed, 22 insertions(+), 1 deletions(-)
diff -
Also known as Paravirtualization level or maximim cpuid function present in
this leaf.
This is just the EAX value for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware
On 09/17/12 10:41, Kevin Wolf wrote:
Am 16.09.2012 12:13, schrieb Peter Lieven:
Hi,
when trying to block migrate a VM from one node to another, the source
VM crashed with the following assertion:
block.c:3829: bdrv_set_in_use: Assertion `bs->in_use != in_use' failed.
Is this sth already addres
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 66 +
1 files changed, 66 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 9ac3076..34d2291 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1265
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Als
On 09/17/12 10:00, Don Slutz wrote:
Send it to stderr before free of the details.
Signed-off-by: Don Slutz
---
v2: Change __FUNCTION__ to __func__
target-i386/cpu.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 57c064f..
Fix duplicate name (kvmclock => kvm_clock2) also.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 12
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 0313cf5..5f9866a 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
This is used to set the cpu object's hypervisor level to the default for
Microsoft's Hypervisor.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 0e4a18d..4120393 100644
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
http://fixunix.com/kernel/538707-use-cpuid-communicate-hypervisor.html
Als
On 09/16/2012 11:31 PM, Stefan Weil wrote:
> Yes, these files show up when doing development, but not only on
> QEMU. They are not at all QEMU specific. I assume that most developers
> also have other projects which they work on, so IMHO ignoring those
> files in their user settings makes more sens
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 11 +++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index bfaee02..89a45b5 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -1975,6 +1975,17 @@ void cpu_x86_cpuid(CPUX86St
These are modeled after x86_cpuid_set_vendor and x86_cpuid_get_vendor.
Since kvm's vendor is shorter, the test for correct size is removed and zero
padding is added.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 44
1 files changed, 44 insertion
These are modeled after x86_cpuid_get_xlevel and x86_cpuid_set_xlevel.
Signed-off-by: Don Slutz
---
target-i386/cpu.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index 5f9866a..0e4a18d 100644
--- a/tar
Also known as Paravirtualization vendor.
This is EBX, ECX, EDX data for 0x4000.
QEMU knows this is KVM_CPUID_SIGNATURE (0x4000).
This is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel chang
Signed-off-by: Don Slutz
---
target-i386/kvm.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index bf27793..b8789f2 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -392,13 +392,15 @@ int kvm_arch_init_vcpu(CPUX86S
Signed-off-by: Don Slutz
---
target-i386/cpu.h |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index 47bc00c..a2d3588 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -799,6 +799,10 @@ typedef struct CPUX86State {
uin
1 - 100 of 265 matches
Mail list logo
