On 04/03/2012 06:15 AM, Paolo Bonzini wrote:
Since most property types do not have a parse property now, this was
broken. Fix it by looking at the setter instead.
Signed-off-by: Paolo Bonzinipbonz...@redhat.com
Reviewed-by: Anthony Liguori aligu...@us.ibm.com
Regards,
Anthony Liguori
---
Tried another approach, that involves only seabios change as specified in
acpi50.spec: 5.6.4 General-Purpose Event Handling
by switching from level to edge handler.
diff --git a/src/acpi-dsdt.dsl b/src/acpi-dsdt.dsl
index 4e04c48..51906ad 100644
--- a/src/acpi-dsdt.dsl
+++ b/src/acpi-dsdt.dsl
@@
On 04/03/2012 06:15 AM, Paolo Bonzini wrote:
Otherwise, non-string properties without a legacy counterpart are missed.
Also fix error propagation in object_property_print itself, otherwise
pointer properties are printed as null.
Signed-off-by: Paolo Bonzinipbonz...@redhat.com
Reviewed-by:
On 04/03/2012 06:15 AM, Paolo Bonzini wrote:
Signed-off-by: Paolo Bonzinipbonz...@redhat.com
---
hw/qdev-properties.c | 22 --
hw/qdev.c| 28 +++-
hw/qdev.h|1 -
3 files changed, 23 insertions(+), 28
2012/4/3 Paul Brook p...@codesourcery.com:
I'm no SPI expert, but a bit of googling suggests that it's
a synchronous duplex bus, so you always send a byte of data
to the slave and get one back in return (even if for some slaves
it might be random garbage).
Waitaminute. So this is
Il 03/04/2012 23:09, Anthony Liguori ha scritto:
On 04/03/2012 06:15 AM, Paolo Bonzini wrote:
Signed-off-by: Paolo Bonzinipbonz...@redhat.com
---
hw/qdev-properties.c | 22 --
hw/qdev.c| 28 +++-
hw/qdev.h|1
From: Jason Wang jasow...@redhat.com
Date: Wed, 28 Mar 2012 13:44:28 +0800
As hypervior does not have the knowledge of guest network configuration, it's
better to ask guest to send gratuitous packets when needed.
Guest tests VIRTIO_NET_S_ANNOUNCE bit during config change interrupt and when
N.B. This is a small patch with significant implications. Please read
carefully.
Right now, '-M pc' is the default and, in general, this machine type has guest
visible ABI changes in each version of QEMU. At some point in each release,
we create a '-M pc-X.Y' corresponding to the last release
This series contains some preliminary patches to my big DMA series.
This adds support for dma_addr_t type properties and uses that to
convert the usb-xhci to use the existing pci dma wrapper functions.
Changes since last version:
* Added copyright notice (GPL v2 or later) to qdev-dma.h
A while back, we introduced the dma_addr_t type, which is supposed to
be used for bus visible memory addresses. At present, this is an
alias for target_phys_addr_t, but this will change when we eventually
add support for guest visible IOMMUs.
There are some instances of target_phys_addr_t in the
Shortly before 1.0, we added helper functions / wrappers for doing PCI DMA
from individual devices. This makes what's going on clearer and means that
when we add IOMMU support somewhere in the future, only the general PCI
code will have to change, not every device that uses PCI DMA.
However,
On Tue, Apr 03, 2012 at 10:53:10AM +0200, Andreas Färber wrote:
Am 03.04.2012 02:51, schrieb David Gibson:
On Mon, Apr 02, 2012 at 09:49:12AM +0200, Andreas Färber wrote:
Am 31.03.2012 10:50, schrieb David Gibson:
On Fri, Mar 30, 2012 at 11:34:25AM +0200, Andreas Färber wrote:
Am
Hi Paul,
Regarding using ssi, theres a few things that come to mind:
Theres no sense of it being a multi-slave bus, its just a point to
point link. SPI devices universally have the notion of the CS pin that
tristates the device of the bus. Masters connect to a number of slaves
and one-hot-decode
The Buildbot has detected a new failure on builder block_mingw32 while building
qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_mingw32/builds/176
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_rhel61
Build Reason:
If the kernel page size is larger than TARGET_PAGE_SIZE, which
happens for example on ppc64 with kernels compiled for 64K pages,
the dirty tracking doesn't work.
Cc: Avi Kivity a...@redhat.com
Cc: Marcelo Tosatti mtosa...@redhat.com
Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
On Tue, Apr 03, 2012 at 09:08:16AM +0200, Jan Kiszka wrote:
On 2012-04-02 06:04, David Gibson wrote:
From: Ben Herrenschmidt b...@kernel.crashing.org
If the kernel page size is larger than TARGET_PAGE_SIZE, which
happens for example on ppc64 with kernels compiled for 64K pages,
the
On Tue, Apr 03, 2012 at 11:43:57PM +0300, Dor Laor wrote:
On 04/03/2012 05:43 PM, Markus Armbruster wrote:
I'm afraid my notes are rather rough...
* 1.1
soft freeze apr 15th (less than two weeks)
hard freeze may 1
three months cycle for 1.2
stable machine types only every few
The Buildbot has detected a new failure on builder block_i386_debian_6_0 while
building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/block_i386_debian_6_0/builds/233
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: yuzuki
Build
Hi,
Could you tell me what kind of programs can be emulated in user-mode of
QEMU ?
It seems that only limited programs can be emulated in user-mode, like
/bin/ls, and with warning. A lot of other programs cannot be emulated, like
GUI programs, browser, etc.
Additionally, why so many
On Tue, Apr 03, 2012 at 06:39:22PM +1200, Alexey Korolev wrote:
Hi Kevin,
Thank you for the patches!
I've created a diff of final version of your changes over mine, to make it
clear what has changed.
Rather than including the complete diff, I've just left relevant parts and
added
How can I monitor the execution of some specific instructions (for
example calls) of an application executing in linux-user mode? My
first idea was inserting an interrupt (creating its proper handler)
before all target instructions but I couldn`t get the it working. Any
ideas on this?
How
Could you tell me what kind of programs can be emulated in user-mode of
QEMU ?
Use-mode can emulate programs compiled for different ISA but with same OS.
It seems that only limited programs can be emulated in user-mode, like
/bin/ls, and with warning. A lot of other programs cannot be
On 03.04.2012 20:45, Peter Maydell wrote:
Hi; I've been working on a refactoring of the ARM GIC code (trying
to make it its own sysbus device rather than having the .c file
included from lots of places), and I noticed the following odd code
in hw/exynos4210_gic.c:exynos4210_gic_init():
Currently the pseries machine contains not one but two somewhat ugly hacks
to allow printing of early debug messages before the guest has properly
read the device tree.
First, we special case H_PUT_TERM_CHAR so that a vtermno of 0 (usually
invalid) will look for a suitable vty and use that. This
Andreas,
Here's another batch of pseries patches. 1-3 are cleanups with little
to no functionality change. 4 implements automatic address allocation
for VIO devices, which makes instantiating them with -device rather
easier.
This is about the third small series of patches I have pending for
On target-ppc, our table of CPU types and features encodes the features as
found on the hardware, regardless of whether these features are actually
usable under TCG or KVM. We already have cases where the information from
the cpu table must be fixed up to account for limitations in the emulation
The VIOsPAPRBus structure, used on the pseries machine contains some old
fields which are no longer used anywhere. This patch removes them.
Cc: qemu-triv...@nongnu.org
Signed-off-by: David Gibson da...@gibson.dropbear.id.au
---
hw/spapr_vio.h |2 --
1 files changed, 0 insertions(+), 2
PAPR virtual IO (VIO) devices require a unique, but otherwise arbitrary,
address used as a token to the hypercalls which manipulate them.
Currently the pseries machine code does an ok job of allocating these
addresses when the legacy -net nic / -serial and so forth options are used
but will fail
201 - 228 of 228 matches
Mail list logo
