Am 13.01.2012 21:52, schrieb Peter Maydell:
Add a definition of a Cortex-A15 CPU. Note that for the moment we do
not implement any of:
* Large Physical Address Extensions (LPAE)
* Virtualization Extensions
* Generic Timer
* TrustZone (this is also true of our existing Cortex-A9 model,
Am 23.01.2012 08:20, schrieb Peter A. G. Crosthwaite:
Device model for Cadence UART
Signed-off-by: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
---
Makefile.target |1 +
hw/cadence_uart.c | 619
+
2 files changed, 620
On 01/23/2012 09:08 PM, Anthony Liguori wrote:
QEMU depends on Python = Python 2 for QAPI, tracing and maybe more.
See scripts/*.py.
I've been thinking that we could potentially rewrite a large chunk
(all?) of configure in python too since we have such a hard dependency now.
What would the
On 01/23/2012 07:14 PM, Thomas Higdon wrote:
Can you please also do the same REPORT LUNS and INQUIRY in hw/scsi-bus.c?
You're talking about the scsi_target_emulate_report_luns() and
scsi_target_emulate_inquiry() functions in hw/scsi-bus.c? By my read of
the code, these appear safe. In both
Acked-by: M. Mohan Kumar mo...@in.ibm.com
On Monday, January 16, 2012 11:41:40 PM Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
When 2c74c2cb4bedddbfa67628fbd5f9273b4e0e9903 added support for
the 'readonly' flag against 9p filesystems, it also made QEMU
add the
On 24 January 2012 07:59, Andreas Färber afaer...@suse.de wrote:
Am 13.01.2012 21:52, schrieb Peter Maydell:
@@ -433,6 +433,7 @@ void cpu_arm_set_cp_io(CPUARMState *env, int cpnum,
#define ARM_CPUID_CORTEXA8 0x410fc080
#define ARM_CPUID_CORTEXA9 0x410fc090
#define ARM_CPUID_CORTEXM3
On 01/23/2012 07:38 PM, Jan Kiszka wrote:
nums=`od -A n -t u1 -v -N $size $1`
-for i in ${nums}; do
-# add each byte's value to sum
-sum=`expr \( $sum + $i \) % 256`
-done
-
-sum=$(( (256 - $sum) % 256 ))
We have a bashism here, so why not do
sum=$(( ($sum + $i) % 256 ))
and do
Am 24.01.2012 07:53, schrieb Andreas Färber:
Am 24.01.2012 04:12, schrieb q...@buildbot.b1-systems.de:
The Buildbot has detected a new failure on builder block_x86_64_debian_6_0
while building qemu.
Full details are available at:
Now that we have a hard dependency on python anyway, we can replace the
slow shell script to calculate the option ROM checksum with a fast AND
portable python version. Tested both with python 2.7 and 3.1.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
Getting v2 vs. v3 running wasn't
A bit late, but here goes anyway:
Luiz Capitulino lcapitul...@redhat.com writes:
From: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
Let's report specific errors so that management tools and users can
identify the problem.
Two new qerrors are needed:
* QERR_DEVICE_HAS_NO_MEDIUM for
Am 23.01.2012 21:37, schrieb Anthony Liguori:
On 01/23/2012 02:32 PM, Jan Kiszka wrote:
On 2012-01-23 21:08, Anthony Liguori wrote:
I've been thinking that we could potentially rewrite a large chunk
(all?) of configure in python too since we have such a hard
dependency now.
Sounds almost
Add machine model pc-1.1
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
hw/pc_piix.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index 744b0dc..ac251c6 100644
--- a/hw/pc_piix.c
+++ b/hw/pc_piix.c
@@
This patch series adds support for CPU ejection callbacks in Seabios and qemu.
This will be needed for proper ACPI vcpu destruction/unplug in conjunction
with the vcpu lifecycle patches.
v1-v2: Add pc-1.1 model with cpu acpi ejection property. Add documentation.
v1 of the series also defined the
Add CPU acpi interface documentation. Move all ACPI documentation (CPU and
PCI) to one file.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
docs/specs/acpi_hotplug.txt | 49 +++
docs/specs/acpi_pci_hotplug.txt | 37
Add bitmap for CPU EJ0 callback and write to it on a cpu _EJ0 callback. Remove
Sleep() call.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
src/acpi-dsdt.dsl |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/src/acpi-dsdt.dsl
Add stub functions for CPU eject callback. Define cpu_acpi_eject property and
enable eject callback only for pc-1.1 machine model.
Signed-off-by: Vasilis Liaskovitis vasilis.liaskovi...@profitbricks.com
---
hw/acpi_piix4.c | 20
hw/pc_piix.c|8
2 files
Hi,
We really should view RAM as just another device so I don't like the
idea of
propagating a global concept of when RAM is restored because that
treats it
specially compared to other devices.
But viewing RAM as just another device, having Xen only restore a
subset of
devices should
On 2012-01-24 11:10, Vasilis Liaskovitis wrote:
Add stub functions for CPU eject callback. Define cpu_acpi_eject property and
enable eject callback only for pc-1.1 machine model.
Just to get the idea: What is the plan and advantage of introducing a
stub first? How much more is required to have
On Tue, Jan 24, 2012 at 6:22 PM, Benjamin mlspira...@gmail.com wrote:
Hello Stefan,
Hi,
Please send QEMU development emails to the mailing list so others can
help or we can avoid duplicating work in case someone else is already
looking into this. I have CCed the mailing list.
I've seen your
On 01/23/2012 07:18 PM, Anthony Liguori wrote:
Generally speaking, RAM is an independent device in most useful cases.
Can you give examples? Do you mean a subdevice with composition, or a
really independent device?
Onboard RAM is a very special case because it's extremely unusual.
What's
On 01/24/2012 12:21 PM, Gerd Hoffmann wrote:
But viewing RAM as just another device, having Xen only restore a
subset of
devices should be a reasonable thing to do moving forward.
I don't think modeling device memory (i.e. vga vram) as something
independent from the device (vga) is a
On 01/24/2012 12:10 PM, Avi Kivity wrote:
But viewing RAM as just another device, having Xen only restore a
subset of devices should be a reasonable thing to do moving forward.
The main problem here I believe is that we have part of the VGA Bios
functionality in the hardware emulation.
Doesn't
On 01/24/2012 01:27 PM, Paolo Bonzini wrote:
On 01/24/2012 12:10 PM, Avi Kivity wrote:
But viewing RAM as just another device, having Xen only restore a
subset of devices should be a reasonable thing to do moving forward.
The main problem here I believe is that we have part of the VGA Bios
On 01/24/2012 12:32 PM, Avi Kivity wrote:
Clearing the screen should only write to the RAM at 0xB8000 (and
perhaps 0xA since IIRC it's where text-mode fonts lie). The
option ROM cannot even assume that the main BIOS knows about the VESA
framebuffer, can it?
Yes, but why should
On Tue, 24 Jan 2012, Avi Kivity wrote:
On 01/24/2012 01:27 PM, Paolo Bonzini wrote:
On 01/24/2012 12:10 PM, Avi Kivity wrote:
But viewing RAM as just another device, having Xen only restore a
subset of devices should be a reasonable thing to do moving forward.
The main problem here I
Stefan Hajnoczi stefa...@gmail.com writes:
On Tue, Jan 24, 2012 at 6:22 PM, Benjamin mlspira...@gmail.com wrote:
Hello Stefan,
Hi,
Please send QEMU development emails to the mailing list so others can
help or we can avoid duplicating work in case someone else is already
looking into this.
On Tue, 24 Jan 2012, Avi Kivity wrote:
On 01/24/2012 12:21 PM, Gerd Hoffmann wrote:
But viewing RAM as just another device, having Xen only restore a
subset of
devices should be a reasonable thing to do moving forward.
I don't think modeling device memory (i.e. vga vram) as
Jan Kiszka jan.kis...@web.de writes:
On 2012-01-21 17:36, Andreas Färber wrote:
Am 21.01.2012 14:43, schrieb Jan Kiszka:
By using strncasecmp, we allow for arbitrary characters after the
on/off string. Fix this by switching to strcasecmp.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
On 2012-01-12 19:37, Andreas Färber wrote:
Am 08.01.2012 17:31, schrieb Andreas Färber:
Am 08.01.2012 13:01, schrieb Gerhard Wiesinger:
On Wed, 4 Jan 2012, Gerhard Wiesinger wrote:
Testscenario:
1.) Boot e.g. OS with VMMouse support (e.g. Windows)
2.) reboot
3.) Boot e.g. OS without
This patchset adds support for (a rather limited version of) the
Cortex-A15 CPU and the Versatile Express A15 daughterboard.
The resulting model is capable of booting a Linux kernel which has
been configured for Cortex-A15 with the Versatile Express extended
memory map and without support for
Instantiate the CLCD on the vexpress motherboard as well as one on
the daughterboard -- the A15 daughterboard does not have a CLCD
and so relies on the motherboard one.
At the moment QEMU doesn't provide infrastructure for selecting
which display device gets to actually show graphics -- the first
When qemu is started with '-S' to freeze at startup and gdb is connected to
inner gdb server, gdb is using by default 16-bit real-mode. Then if we put
a breakpoint inside kernel linux, the CPU is switched to 32/64-bit protected
mode but GDB is always in 16 bit real-mode. The size of the registers
A device reset does not affect the link state, only set_link does.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/pcnet.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/hw/pcnet.c b/hw/pcnet.c
index 306dc6e..6aa48e0 100644
--- a/hw/pcnet.c
+++ b/hw/pcnet.c
@@
A device reset does not affect the link state, only set_link does.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/e1000.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/hw/e1000.c b/hw/e1000.c
index 86c5416..76e736f 100644
--- a/hw/e1000.c
+++ b/hw/e1000.c
On 2012-01-24 13:47, Jan Kiszka wrote:
A device reset does not affect the link state, only set_link does.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/pcnet.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/hw/pcnet.c b/hw/pcnet.c
index
On 2012-01-24 13:47, Jan Kiszka wrote:
A device reset does not affect the link state, only set_link does.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/e1000.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/hw/e1000.c b/hw/e1000.c
index
Hello,
On Tue, Jan 24, 2012 at 1:40 PM, Laurent Vivier laur...@vivier.eu wrote:
By adding a breakpoint at startup, we can connect GDB to qemu gdb server
when CPU is already in protected mode.
Not tried yet, but usefull workaround IMHO.
Thanks !
--
Francis
Am 24.01.2012 11:28, schrieb Jan Kiszka:
On 2012-01-24 11:10, Vasilis Liaskovitis wrote:
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index ac251c6..6d61567 100644
--- a/hw/pc_piix.c
+++ b/hw/pc_piix.c
@@ -380,6 +380,14 @@ static QEMUMachine pc_machine_v1_1 = {
.desc = Standard PC,
Add a model of the Cortex-A15 memory mapped private peripheral
space. This is fairly simple because the only memory mapped
bit of the A15 is the GIC.
Note that we don't currently model a VGIC and therefore don't
map the VGIC related bits of the GIC.
Signed-off-by: Peter Maydell
The arm_boot secondary boot loader code needs the address of
the GIC CPU interface. Obtaining this from the base address
of the private peripheral region was possible for A9 and 11MPcore,
but the A15 puts the GIC CPU interface in a different place.
So make boards pass in the GIC CPU interface
Add a definition of a Cortex-A15 CPU. Note that for the moment we do
not implement any of:
* Large Physical Address Extensions (LPAE)
* Virtualization Extensions
* Generic Timer
* TrustZone (this is also true of our existing Cortex-A9 model, etc)
This CPU model is sufficient to boot a Linux
Factor out daughterboard specifics into a data structure and
daughterboard initialization function, in preparation for adding
vexpress-a15 support.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/vexpress.c | 118 -
1 files
On 2012-01-24 13:52, Andreas Färber wrote:
Am 24.01.2012 11:28, schrieb Jan Kiszka:
On 2012-01-24 11:10, Vasilis Liaskovitis wrote:
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index ac251c6..6d61567 100644
--- a/hw/pc_piix.c
+++ b/hw/pc_piix.c
@@ -380,6 +380,14 @@ static QEMUMachine
On 01/22/2012 03:06 PM, Blue Swirl wrote:
Let's compile Cirrus in hwlib.
http://repo.or.cz/r/qemu/blueswirl.git
Patches look fine (after fixing #2). But please post patches using
git-send-email, otherwise they're unthreaded and lose their grouping as
soon as someone replies.
--
error
Pull the addresses used for mapping motherboard peripherals into
memory out into a table. This will allow us to simply provide a
second table to implement the Cortex-A Series memory map used by
the A15 variant of Versatile Express, as well as the current
Legacy map used by A9.
Signed-off-by:
On 01/24/2012 05:10 AM, Avi Kivity wrote:
On 01/23/2012 07:18 PM, Anthony Liguori wrote:
Generally speaking, RAM is an independent device in most useful cases.
Can you give examples? Do you mean a subdevice with composition, or a
really independent device?
I expect we'll have one Ram
On 01/24/2012 05:52 AM, Stefano Stabellini wrote:
On Tue, 24 Jan 2012, Avi Kivity wrote:
On 01/24/2012 01:27 PM, Paolo Bonzini wrote:
On 01/24/2012 12:10 PM, Avi Kivity wrote:
But viewing RAM as just another device, having Xen only restore a
subset of devices should be a reasonable thing to
On real Versatile Express hardware, the boot ROM puts the secondary
CPU bootcode/holding pen in SRAM. We can therefore rely on Linux not
trashing this memory until secondary CPUs have booted up, and can
put our QEMU-specific pen code in the same place. This allows us to
drop the odd hack RAM page
On 01/24/2012 05:13 AM, Avi Kivity wrote:
On 01/24/2012 12:21 PM, Gerd Hoffmann wrote:
But viewing RAM as just another device, having Xen only restore a
subset of
devices should be a reasonable thing to do moving forward.
I don't think modeling device memory (i.e. vga vram) as something
Add a dummy implementation of the cp15 registers for the generic
timer (found in the Cortex-A15), just sufficient for Linux to
decide that it can't use it. This requires at least CNTP_CTL and
CNTFRQ to be implemented as RAZ/WI; we RAZ/WI all of c14.
Signed-off-by: Peter Maydell
Add the vexpress-a15 machine, and the A-Series memory map it uses.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/vexpress.c | 141 +
1 files changed, 141 insertions(+), 0 deletions(-)
diff --git a/hw/vexpress.c
On 01/24/2012 04:21 AM, Gerd Hoffmann wrote:
Hi,
We really should view RAM as just another device so I don't like the
idea of
propagating a global concept of when RAM is restored because that
treats it
specially compared to other devices.
But viewing RAM as just another device, having Xen
Am 15.12.2011 11:14, schrieb Li Zhi Hui:
Signed-off-by: Li Zhi Hui zhihu...@linux.vnet.ibm.com
---
block/qcow.c | 56 +---
1 files changed, 37 insertions(+), 19 deletions(-)
Thanks, applied to the block branch.
Kevin
Avi Kivity a...@redhat.com writes:
On 01/22/2012 03:06 PM, Blue Swirl wrote:
Let's compile Cirrus in hwlib.
http://repo.or.cz/r/qemu/blueswirl.git
Patches look fine (after fixing #2). But please post patches using
git-send-email, otherwise they're unthreaded and lose their grouping as
Am 21.11.2011 08:40, schrieb Li Zhi Hui:
Since common file operation functions lack of error detection and use much
more I/O syscalls,
so change them to bdrv series functions and reduce I/O request.
v2: avoid malloc a large memory
v1: convert file operation functions to bdrv functions and
Am 23.01.2012 18:15, schrieb Thomas Higdon:
This prevents the emulated SCSI device from trying to DMA more bytes to the
initiator than are expected. Without this, the SCRIPTS code in the emulated
LSI
device eventually raises a DMA interrupt for a data overrun when an INQUIRY
command whose
On 01/23/2012 11:38 AM, Markus Armbruster wrote:
Please send in any agenda items you are interested in covering.
I don't have anything pressing. I vote to cancel the call.
Regards,
Anthony Liguori
Cheers,
Markus
On 01/24/2012 02:57 PM, Anthony Liguori wrote:
Please send in any agenda items you are interested in covering.
I don't have anything pressing. I vote to cancel the call.
Nothing that cannot be discussed by email, but anyway here are a couple
of topics:
* qtest/libos: Python or C?
* QOM
On 01/19/2012 08:54 PM, Jan Kiszka wrote:
Nope, see kvm_irqchip_create, patch 13. You can also check by browsing
the qtree (different device model names).
That was my biggest objection to the previous iterations. Later
versions changed to use an attribute (selecting the backend). What
On 01/24/2012 08:03 AM, Paolo Bonzini wrote:
On 01/24/2012 02:57 PM, Anthony Liguori wrote:
Please send in any agenda items you are interested in covering.
I don't have anything pressing. I vote to cancel the call.
Nothing that cannot be discussed by email, but anyway here are a couple of
On 2012-01-24 15:05, Avi Kivity wrote:
On 01/19/2012 08:54 PM, Jan Kiszka wrote:
Nope, see kvm_irqchip_create, patch 13. You can also check by browsing
the qtree (different device model names).
That was my biggest objection to the previous iterations. Later
versions changed to use an
On 01/24/2012 04:10 PM, Jan Kiszka wrote:
On 2012-01-24 15:05, Avi Kivity wrote:
On 01/19/2012 08:54 PM, Jan Kiszka wrote:
Nope, see kvm_irqchip_create, patch 13. You can also check by browsing
the qtree (different device model names).
That was my biggest objection to the previous
Am 24.01.2012 15:08, schrieb Anthony Liguori:
On 01/24/2012 08:03 AM, Paolo Bonzini wrote:
On 01/24/2012 02:57 PM, Anthony Liguori wrote:
Please send in any agenda items you are interested in covering.
I don't have anything pressing. I vote to cancel the call.
Nothing that cannot be
Anthony Liguori anth...@codemonkey.ws writes:
On 01/23/2012 11:38 AM, Markus Armbruster wrote:
Please send in any agenda items you are interested in covering.
I don't have anything pressing. I vote to cancel the call.
Call's cancelled.
On 01/24/2012 03:30 PM, Kevin Wolf wrote:
* qtest/libos: Python or C?
Both.
More importantly: When?:-)
Are there still any problems that must be fixed before it can be merged?
There was no discussion on my alternative proposal on IRQ interception.
Which might mean it's all fine and
On Tue, Jan 24, 2012 at 11:28:41AM +0100, Jan Kiszka wrote:
On 2012-01-24 11:10, Vasilis Liaskovitis wrote:
Add stub functions for CPU eject callback. Define cpu_acpi_eject property
and
enable eject callback only for pc-1.1 machine model.
Just to get the idea: What is the plan and
Am 18.01.2012 15:59, schrieb Stefan Hajnoczi:
The qemu-img.c:is_not_zero() function checks if a buffer contains all
zeroes. This function will come in handy for zero-detection in the
block layer, so clean it up and move it to cutils.c.
Note that the function now returns true if the buffer
On 2012-01-18 11:33, Paolo Bonzini wrote:
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/pc_piix.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/hw/pc_piix.c b/hw/pc_piix.c
index 2aba89c..3f92bf9 100644
--- a/hw/pc_piix.c
+++ b/hw/pc_piix.c
@@
Am 18.01.2012 15:59, schrieb Stefan Hajnoczi:
The ability to zero regions of an image file is a useful primitive for
higher-level features such as image streaming or zero write detection.
Image formats may support an optimized metadata representation instead
of writing zeroes into the image
On 01/24/2012 01:53 AM, Jan Kiszka wrote:
Now that we have a hard dependency on python anyway, we can replace the
slow shell script to calculate the option ROM checksum with a fast AND
portable python version. Tested both with python 2.7 and 3.1.
Signed-off-by: Jan Kiszka
On 2012-01-24 16:22, Eric Blake wrote:
On 01/24/2012 01:53 AM, Jan Kiszka wrote:
Now that we have a hard dependency on python anyway, we can replace the
slow shell script to calculate the option ROM checksum with a fast AND
portable python version. Tested both with python 2.7 and 3.1.
When an input line is handled as level-triggered, it will immediately
raise an IRQ on the output of a PIC again that goes through an init
reset. So only clear the edge-triggered inputs from IRR in that
scenario.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/i8259.c|2 +-
On 01/24/2012 08:05 AM, Avi Kivity wrote:
On 01/19/2012 08:54 PM, Jan Kiszka wrote:
Nope, see kvm_irqchip_create, patch 13. You can also check by browsing
the qtree (different device model names).
That was my biggest objection to the previous iterations. Later
versions changed to use an
On 01/24/2012 08:13 AM, Avi Kivity wrote:
On 01/24/2012 04:10 PM, Jan Kiszka wrote:
On 2012-01-24 15:05, Avi Kivity wrote:
On 01/19/2012 08:54 PM, Jan Kiszka wrote:
Nope, see kvm_irqchip_create, patch 13. You can also check by browsing
the qtree (different device model names).
That was my
On 01/24/2012 02:00 PM, Stefano Stabellini wrote:
On Tue, 24 Jan 2012, Avi Kivity wrote:
On 01/24/2012 12:21 PM, Gerd Hoffmann wrote:
But viewing RAM as just another device, having Xen only restore a
subset of
devices should be a reasonable thing to do moving forward.
I
On 01/24/2012 03:18 PM, Anthony Liguori wrote:
On 01/24/2012 05:13 AM, Avi Kivity wrote:
On 01/24/2012 12:21 PM, Gerd Hoffmann wrote:
But viewing RAM as just another device, having Xen only restore a
subset of
devices should be a reasonable thing to do moving forward.
I don't think
On 01/24/2012 03:25 PM, Anthony Liguori wrote:
To my understanding, QXL will break identically on Xen for the same
reason: the reset handler assumes it can deal with the VRAM as it
likes.
Yes. Some data structures for host- guest communication are living
in device memory, and a reset
On 01/24/2012 01:44 PM, Paolo Bonzini wrote:
On 01/24/2012 12:32 PM, Avi Kivity wrote:
Clearing the screen should only write to the RAM at 0xB8000 (and
perhaps 0xA since IIRC it's where text-mode fonts lie). The
option ROM cannot even assume that the main BIOS knows about the
VESA
Jan Kiszka jan.kis...@siemens.com writes:
On 2012-01-24 16:22, Eric Blake wrote:
On 01/24/2012 01:53 AM, Jan Kiszka wrote:
Now that we have a hard dependency on python anyway, we can replace the
slow shell script to calculate the option ROM checksum with a fast AND
portable python version.
On 01/24/2012 03:14 PM, Anthony Liguori wrote:
On 01/24/2012 05:10 AM, Avi Kivity wrote:
On 01/23/2012 07:18 PM, Anthony Liguori wrote:
Generally speaking, RAM is an independent device in most useful cases.
Can you give examples? Do you mean a subdevice with composition, or a
really
Current master dies for me:
$ upstream-qemu -nodefaults -S -m 384 -vnc :0 -device cirrus-vga
RAMBlock vga.vram already registered, abort!
Aborted (core dumped)
git-bisect blames this one:
Blue Swirl blauwir...@gmail.com writes:
Improve VGA selection logic, push check for device availabilty to
On 01/23/2012 06:55 PM, Jan Kiszka wrote:
On 2012-01-23 17:29, Igor Mammedov wrote:
On 01/17/2012 03:17 PM, Jan Kiszka wrote:
It seams that env-cpuid_apic_id = cpu is pointless especcialy
taking in account that in cpu_x86_init cpuid_apic_id is initialized
by cpu_index.
What we gain in having
On Fri, 13 Jan 2012 20:52:39 +, Peter Maydell peter.mayd...@linaro.org
wrote:
From: Mark Langsdorf mark.langsd...@calxeda.com
Increase the maximum number of GIC interrupts for a9mp and a11mp to 1020,
and create a configurable property for each defaulting to 96 and 64
(respectively) so
hello,
I'm learning uefi http://en.wikipedia.org/wiki/Uefi and qemu.
If I understand correctly, in uefi, device drivers contain at least three
functions: supported, start and stop. When PCI devices are discovered, all
drivers supported function is invoked and if this function returns true,
its
On 2012-01-24 17:24, Igor Mammedov wrote:
On 01/23/2012 06:55 PM, Jan Kiszka wrote:
On 2012-01-23 17:29, Igor Mammedov wrote:
On 01/17/2012 03:17 PM, Jan Kiszka wrote:
It seams that env-cpuid_apic_id = cpu is pointless especcialy
taking in account that in cpu_x86_init cpuid_apic_id is
And I have this bug!
Linux test-2 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:52:42 UTC 2010
x86_64 GNU/Linux
In container i have Windows XP SP3
In log:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32
On 01/23/12 20:16, Stefan Weil wrote:
Am 23.01.2012 19:38, schrieb Jan Kiszka:
Forking an expr process for every byte of the input data slows down the
checksum calculation massively. Fix this while still remaining portable
by implementing the algorithm in awk.
Signed-off-by: Jan
And more: i have too more virtual PC with WindowsXP SP3 and with one
CPU, but them doesnt have any problems. Maybe this bug depends on 2 and
more CPU??
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
From: Andreas Färber andreas.faer...@web.de
VMState supports the type bool but qdev instead supports bit, backed by
uint32_t. Therefore let's add DEFINE_PROP_BOOL() and qdev_prop_set_bool().
bool by definition is either true or false. Should the need arise to
parse yes/no, on/off, 1/0 or
On Tue, Jan 24, 2012 at 08:53:03AM -0500, Kevin Wolf wrote:
Am 23.01.2012 18:15, schrieb Thomas Higdon:
This prevents the emulated SCSI device from trying to DMA more bytes to the
initiator than are expected. Without this, the SCRIPTS code in the emulated
LSI
device eventually raises a
Hi all,
I assume that I found a possible source of the bad usbtablet update rate.
I did some git bisectioning but I didn't get a usable result due to too
many merges (or maybe my little knowledge to git), so I proceeded with some
manual bisectioning by manually selecting commits and tested
On 2012-01-24 18:17, Andreas Färber wrote:
From: Andreas Färber andreas.faer...@web.de
VMState supports the type bool but qdev instead supports bit, backed by
uint32_t. Therefore let's add DEFINE_PROP_BOOL() and qdev_prop_set_bool().
bool by definition is either true or false. Should the
On Tue, Jan 24, 2012 at 15:57, Markus Armbruster arm...@redhat.com wrote:
Current master dies for me:
$ upstream-qemu -nodefaults -S -m 384 -vnc :0 -device cirrus-vga
RAMBlock vga.vram already registered, abort!
Aborted (core dumped)
git-bisect blames this one:
Blue Swirl
From: Sergei Trofimovich sly...@gentoo.org
Signed-off-by: Sergei Trofimovich sly...@gentoo.org
---
configure |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 9d72145..bca1943 100755
--- a/configure
+++ b/configure
@@ -771,6 +771,10 @@ for
Am 24.01.2012 18:29, schrieb Jan Kiszka:
On 2012-01-24 18:17, Andreas Färber wrote:
From: Andreas Färber andreas.faer...@web.de
VMState supports the type bool but qdev instead supports bit, backed by
uint32_t. Therefore let's add DEFINE_PROP_BOOL() and qdev_prop_set_bool().
bool by
On 01/24/2012 09:56 AM, Avi Kivity wrote:
On 01/24/2012 03:14 PM, Anthony Liguori wrote:
On 01/24/2012 05:10 AM, Avi Kivity wrote:
On 01/23/2012 07:18 PM, Anthony Liguori wrote:
Generally speaking, RAM is an independent device in most useful cases.
Can you give examples? Do you mean a
On 01/24/2012 11:38 AM, Andreas Färber wrote:
Am 24.01.2012 18:29, schrieb Jan Kiszka:
On 2012-01-24 18:17, Andreas Färber wrote:
From: Andreas Färberandreas.faer...@web.de
VMState supports the type bool but qdev instead supports bit, backed by
uint32_t. Therefore let's add DEFINE_PROP_BOOL()
On 2012-01-24 18:38, Andreas Färber wrote:
Am 24.01.2012 18:29, schrieb Jan Kiszka:
On 2012-01-24 18:17, Andreas Färber wrote:
From: Andreas Färber andreas.faer...@web.de
VMState supports the type bool but qdev instead supports bit, backed by
uint32_t. Therefore let's add DEFINE_PROP_BOOL()
On 2012-01-24 18:24, Erik Rull wrote:
Hi all,
I assume that I found a possible source of the bad usbtablet update rate.
I did some git bisectioning but I didn't get a usable result due to too
many merges (or maybe my little knowledge to git), so I proceeded with some
manual bisectioning
Am 24.01.2012 08:22, schrieb Andreas Färber:
Am 23.01.2012 08:20, schrieb Peter A. G. Crosthwaite:
Added linux specific kernel dtb option. This option can be specified
to inject
an argument device tree blob (dtb) into linux.
Signed-off-by: Peter A. G. Crosthwaite
1 - 100 of 161 matches
Mail list logo
