于 2013-2-20 4:51, Eric Blake 写道:
On 02/18/2013 07:09 AM, Wenchao Xia wrote:
This patch added the support of showing internal snapshots on a
single block device in hmp layer, by simply change parameter in
s/change/changing a/
calling of qmp funtion.
s/funtion/function/
OK.
Signed-
于 2013-2-21 7:30, Eric Blake 写道:
On 02/20/2013 03:57 PM, Eric Blake wrote:
On 02/18/2013 03:46 PM, Wenchao Xia wrote:
Hi, Eric
About the interface,there is actually requirement to know internal
snapshots in an image of a backing file, so I think the API should be
improved as:
# @query-snaps
于 2013-2-20 7:04, Eric Blake 写道:
On 02/18/2013 07:09 AM, Wenchao Xia wrote:
This patch add function bdrv_query_image_info(), which will return
image info in qmp object format. The implementation code are based
on the code moved from qemu-img.c, but use block layer function to get
snapshot inf
于 2013-2-20 5:24, Eric Blake 写道:
On 02/18/2013 07:09 AM, Wenchao Xia wrote:
Signed-off-by: Wenchao Xia
---
block.c | 81 +
include/block/block.h |4 ++
qemu-img.c| 81 --
On 02/25/2013 06:01 PM, Michael S. Tsirkin wrote:
> On Mon, Feb 25, 2013 at 02:11:44PM +0800, Jason Wang wrote:
>> On 02/25/2013 01:57 PM, Jason Wang wrote:
>>> On 02/24/2013 05:54 AM, Michael S. Tsirkin wrote:
On Sat, Feb 23, 2013 at 10:49:29PM +0200, Michael S. Tsirkin wrote:
> On Fri, F
virtio-console.c used to return a value less than the number of bytes
asked to be written out to a chardev backend in case the backend is not
writable. virtio-serial-bus.c then implicitly enabled flow control for
that port.
Make this explicit instead.
Signed-off-by: Amit Shah
---
hw/virtio-con
Hi,
This is an add-on patch to the series Anthony posted introducing flow
control for chardevs.
The previous logic relied on a <= nr_bytes return to the 'write'
function, which indicated a short write, triggering flow control in
the virtio-serial-bus code. This change explicitly asks the
virtio-
Currently, for the pseries machine the device tree supplied by qemu to SLOF
and from there to the guest does not include a 'compatible property' at the
root level. Usually that works fine, since in this case the compatible
property doesn't really give any information not already found in the
'devi
For real i440fx, its TOM is fixed to 1G, I think Xen or other VMMs playing with
Qemu should break this hardware rule. Maybe we can implement this register as
a write-only one, so that OS can't see its existence. If OS reads this
register, Qemu always return 0xff, and for any write operations
> -Original Message-
> From: qemu-devel-bounces+xudong.hao=intel@nongnu.org
> [mailto:qemu-devel-bounces+xudong.hao=intel@nongnu.org] On Behalf
> Of Stefano Stabellini
> Sent: Tuesday, February 26, 2013 12:06 AM
> To: Hao, Xudong
> Cc: aligu...@us.ibm.com; Stefano Stabellini; m...@r
On Mon, Feb 25, 2013 at 01:19:48PM +0100, Alexander Graf wrote:
>
> On 21.02.2013, at 03:41, David Gibson wrote:
>
> > For PAPR guests, KVM tracks the various areas registered with the
> > H_REGISTER_VPA hypercall. For full emulation, of course, these are tracked
> > within qemu. At present the
On Mon, Feb 25, 2013 at 10:03:33AM +0100, Gerd Hoffmann wrote:
> This patch add support for a new way to initialize chardev devices.
> Instead of calling a initialization function with a QemuOpts we will
> now create a (qapi) ChardevBackend, optionally call a function to
> fill ChardevBackend from
On Mon, Feb 25, 2013 at 10:51:55AM +0200, Gleb Natapov wrote:
> On Sun, Feb 24, 2013 at 01:00:28PM -0500, Kevin O'Connor wrote:
> > I did a review of the SeaBIOS code to see what information is
> > currently used to generate the ACPI, SMBIOS, MPTABLE, and PIR bios
> > tables. Here's what I came up
Orit Wasserman wrote:
> Instead of using cache_insert do the update itself
>
> Signed-off-by: Orit Wasserman
> ---
> page_cache.c | 16 ++--
> 1 file changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/page_cache.c b/page_cache.c
> index 748957b..21a4cde 100644
> --- a/page_ca
You know the inet sockets in qemu:
...
-net socket,vlan=1,connect=127.0.0.1:47654
...
Well, a bug I looked into lead me to code a very simple process doing a
"cable" between two machines connected with this config. This setup gave
surprising results and lead me to compare ping timings between this
On 02/25/2013 02:03 AM, Gerd Hoffmann wrote:
> This patch adds 'stdio' support to qapi and also switches over the
> stdio chardev initialization to the new qapi code path.
>
> Signed-off-by: Gerd Hoffmann
> ---
> qapi-schema.json | 14 +-
> qemu-char.c | 26 +
Il 25/02/2013 18:56, Marc-André Lureau ha scritto:
> +
> +static gboolean
> +do_socket(GIOChannel *source,
> + GIOCondition condition,
> + gpointer data)
Extracting do_socket should be a separate patch...
Paolo
- Mensaje original -
> Il 25/02/2013 18:56, Marc-André Lureau ha scritto:
> > LINK = $(call quiet-command,\
> > $(if $(filter %.lo %.la,$^),$(LIBTOOL) --mode=link --tag=CC
> > \
> > )$(CC) $(QEMU_CFLAGS) $(CFLAGS) $(LDFLAGS) $(LIBTOOLFLAGS)
> > -o $@ \
> >
Implement the SYS_CFG_OSC function. Since the idea of
programmable clock rates doesn't make much sense for QEMU,
we simply allow the clock rate to be read back as written.
The number and value of the daughterboard oscillators varies
between daughterboards, so we provide an array property to
allow t
Older glib doesn't implement g_poll(). Most notably the glib version in use
on SLE11 is on 2.18 which is hit by this.
We do want to use g_poll() in the source however. So on older systems, just
wrap it with functions that do exist on older versions.
Signed-off-by: Anthony Liguori
Signed-off-by:
On 22.02.2013, at 12:47, Paolo Bonzini wrote:
> Il 22/02/2013 11:07, Laurent Desnogues ha scritto:
>>> The g_poll(3) interface is a portable version of the poll(2) system call.
>>> The
difference to select(2) is that fine-grained events (G_IO_IN, G_IO_OUT,
G_IO_HUP, G_IO_ERR, G_IO_PRI
From: Marc-André Lureau
---
libcacard/vscclient.c | 314 ++
1 file changed, 162 insertions(+), 152 deletions(-)
diff --git a/libcacard/vscclient.c b/libcacard/vscclient.c
index 9b744f2..5e00db3 100644
--- a/libcacard/vscclient.c
+++ b/libcacard/vs
Compile and link with version.lo
Signed-off-by: Marc-André Lureau
---
Makefile | 8 ++--
rules.mak | 3 ++-
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index 2262410..5f0ded1 100644
--- a/Makefile
+++ b/Makefile
@@ -148,11 +148,15 @@ recurse-all: $(SUB
** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/498417
Title:
cache=writeback on disk image doesn't do write-back
Status in QEMU:
New
Bug desc
self nack, it fails to link without libtool
On 02/24/2013 09:00 PM, Doug Goldstein wrote:
Handle errors and cleanup from the error in a unified place for
parse_acl_file().
Signed-off-by: Doug Goldstein
CC: Anthony Liguori
CC: Richa Marwaha
CC: Corey Bryant
TO: qemu-devel@nongnu.org
---
qemu-bridge-helper.c | 32 +++
This series seems reasonable to me. I just have some comments on
implementation details.
On 02/24/2013 09:00 PM, Doug Goldstein wrote:
Allow the bridge helper to take a config directory rather than having to
specify every file in the directory manually via an include statement.
Signed-off-by:
Hello Stefan,
I coded a socket-based cable between 2 vanilla kvm, here are the commands
to do:
tar xvf qemu_test_sock.tar.gz
cd qemu_test_sock
make
./qemu_test_sock
kvm \
-nodefaults \
-nographic \
-serial stdio \
-drive file=guest1,media=disk,if=virtio \
-device virti
This version handles non-blocking sending and receiving from the
socket.
Signed-off-by: Marc-André Lureau
---
libcacard/vscclient.c | 391 +++---
1 file changed, 246 insertions(+), 145 deletions(-)
diff --git a/libcacard/vscclient.c b/libcacard/vsccli
From: Marc-André Lureau
---
libcacard/vscclient.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/libcacard/vscclient.c b/libcacard/vscclient.c
index 5e00db3..5f47634 100644
--- a/libcacard/vscclient.c
+++ b/libcacard/vscclient.c
@@ -218,8 +218,7 @@ on_host_init(VSCM
It is needed to give that flag to the linker as well, but latest
libtool 2.4.2 still swallows that argument, so let's pass it with
libtool -Wc argument.
qemu-1.4.0/stubs/arch-query-cpu-def.c:6: undefined reference to
`__stack_chk_guard'
Signed-off-by: Marc-André Lureau
---
configure | 8 ++
From: Marc-André Lureau
vscclient needs to call socket_init() for portability.
Moving to osdep.c since it has no internal dependency.
Signed-off-by: Marc-André Lureau
---
util/osdep.c| 23 +++
util/qemu-sockets.c | 24
2 files changed, 23 in
Am 25.02.2013 21:11, schrieb Dmitry Fleytman:
[snip]
> +static int
> +vmxnet3_msix_load(QEMUFile *f, void *opaque, int version_id)
> +{
> +msix_load(&((VMXNET3State *)opaque)->dev, f);
Apart from doing too much in one line, you should not access the parent
field ->dev directly but use PCI_DEVI
This makes the mem MemoryRegion available to derived instance_inits.
Keep the bus in realize for now since naming breaks in instance_init.
Signed-off-by: Andreas Färber
---
hw/usb/hcd-ehci-pci.c| 19 ++-
hw/usb/hcd-ehci-sysbus.c | 16 +---
hw/usb/hcd-ehci.c
Signed-off-by: Anthony Green
---
MAINTAINERS | 5 +
arch_init.c | 2 ++
configure | 12 +++-
cpu-exec.c| 2 ++
default-configs/moxie-softmmu.mak | 2 ++
qapi-schema.json |
Signed-off-by: Anthony Green
---
disas.c | 6 +
disas/Makefile.objs | 1 +
disas/moxie.c | 360
include/disas/bfd.h | 66 +-
4 files changed, 401 insertions(+), 32 deletions(-)
create mode 100644 disas/moxie.c
Signed-off-by: Anthony Green
---
hw/moxie/Makefile.objs | 6 ++
hw/moxie/moxiesim.c| 175 +
include/sysemu/arch_init.h | 1 +
3 files changed, 182 insertions(+)
create mode 100644 hw/moxie/Makefile.objs
create mode 100644 hw/moxie/mox
One of the patches in v2 of this patch set was botched. This one is clean.
Sorry about that, and thanks in advance...
Anthony Green
Anthony Green (4):
Add moxie target code
Add moxie disassembler
Add sample moxie system
Add top level changes for moxie
MAINTAINERS
Am 21.02.2013 21:57, schrieb Eduardo Habkost:
> On Thu, Feb 21, 2013 at 09:23:22PM +0100, Markus Armbruster wrote:
>> Eduardo Habkost writes:
>>
>>> This allows "," to be used a separator between each CPU range. Note
>>> that commas inside key=value command-line options have to be escaped
>>> usi
On 02/21/2013 01:57 PM, Eduardo Habkost wrote:
>>> Note that the following format, currently used by libvirt:
>>>
>>> -numa nodes,cpus=A,B,C,D
>>>
>>> will _not_ work yet, as "," is the option separator for the command-line
>>> option parser, and it will require changing the -numa option parsing
Done.
On Thu, Feb 21, 2013 at 12:47 PM, Stefan Hajnoczi wrote:
> Hi Dmitry,
> The net multiqueue feature went into QEMU 1.4 and conflicts with vmxnet3.c.
>
> Please post a rebased version onto qemu.git/master so vmxnet3 can be
> merged. I'm currently getting the following compiler errors with
>
From: Richard Henderson
While T0+~T1+CF = T0-T1+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Using the ~T1 makes the add and subtract code paths nearly
identical, so have sbc_CC use adc_CC.
Cc: Peter Maydell
Reported-b
> >>> If we use nbd, how can we pass additional information to the other
> >>> side, for example information about unallocated regions?
> >>>
> >>
> >> You can either send trim commands, or just skip those regions and let
> >> the other side figure it out.
> >
> > But we are lost if we want to tran
Signed-off-by: Dmitry Fleytman
Signed-off-by: Yan Vugenfirer
---
include/net/checksum.h | 8
net/checksum.c | 28
2 files changed, 36 insertions(+)
diff --git a/include/net/checksum.h b/include/net/checksum.h
index 3e7b93d..b1cf18a 100644
--- a/inc
This set of patches implements VMWare VMXNET3 paravirtual NIC device.
The device supports of all the device features including offload capabilties,
VLANs and etc.
The device is tested on different OSes:
Fedora 15
Ubuntu 10.4
Centos 6.2
Windows 2008R2
Windows 2008 64bit
Windo
Am 25.02.2013 21:11, schrieb Dmitry Fleytman:
> Signed-off-by: Dmitry Fleytman
> Signed-off-by: Yan Vugenfirer
> ---
> include/net/checksum.h | 8
> net/checksum.c | 28
> 2 files changed, 36 insertions(+)
>
> diff --git a/include/net/checksum.h b/
On 25 February 2013 19:07, Alex Barcelo wrote:
> I'm struggling with the code to understand the "duty and soul" of the
> "qemu_cpu_is_self" function (@cpus.c), and I quite not get it.
>
> I see that this function is called from some points. E.g., from
> tcg_hangle_interrupt and run_on_cpu. Amongst
Am 25.02.2013 21:16, schrieb Peter Maydell:
> Hi; here's a pullreq which just contain's RTH's two
> patches which fix the bad breakage of target-arm.
> Please pull ASAP :-)
>
> thanks
> -- PMM
>
>
> The following changes since commit a345481baa2b2fb3d54f8c9ddb58dfcaf75786df:
>
> target-mips:
Am 25.02.2013 20:07, schrieb Alex Barcelo:
> I'm struggling with the code to understand the "duty and soul" of the
> "qemu_cpu_is_self" function (@cpus.c), and I quite not get it.
>
> I see that this function is called from some points. E.g., from
> tcg_hangle_interrupt and run_on_cpu. Amongst oth
Hi; here's a pullreq which just contain's RTH's two
patches which fix the bad breakage of target-arm.
Please pull ASAP :-)
thanks
-- PMM
The following changes since commit a345481baa2b2fb3d54f8c9ddb58dfcaf75786df:
target-mips: fix for sign-issue in MULQ_W helper (2013-02-23 22:20:45 +0100)
a
From: Peter Crosthwaite
commits 49b4c31efcce45ab714f286f14fa5d5173f9069d and
2de68a4900ef6eb67380b0c128abfe1976bc66e8 reworked the implementation of adc_CC
and sub_CC. The new implementations (on the TCG_TARGET_HAS_add2_i32 code path)
are incorrect. The new logic is:
CF:NF = 0:A +/- 0:CF
CF:NF =
While ~T0+T1+CF = T1-T0+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Cc: Alexander Graf
Signed-off-by: Richard Henderson
---
target-ppc/translate.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --
Signed-off-by: Dmitry Fleytman
Signed-off-by: Yan Vugenfirer
---
hw/Makefile.objs | 1 +
hw/vmxnet_rx_pkt.c | 187 ++
hw/vmxnet_rx_pkt.h | 174
hw/vmxnet_tx_pkt.c | 567 +
hw/vmxnet_tx_pkt.h | 148 ++
net_checksum_add_cont()
checksum calculation for scattered data with odd chunk sizes
net_raw_checksum()
checksum calculation for a buffer
Signed-off-by: Dmitry Fleytman
Signed-off-by: Yan Vugenfirer
---
include/net/checksum.h | 14 +-
net/checksum.c | 13 +++--
2 fi
Signed-off-by: Dmitry Fleytman
Signed-off-by: Yan Vugenfirer
---
hw/vmware_utils.h | 143 ++
hw/vmxnet_debug.h | 115 ++
include/net/eth.h | 347 ++
net/Makefile.objs | 1 +
net/eth.c | 217
While T0+~T1+CF = T0-T1+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Using the ~T1 makes the add and subtract code paths nearly
identical, so have sbc_CC use adc_CC.
Cc: Peter Maydell
Reported-by: Laurent Desnogues
Sign
@John,
with that patch applied on top of 1.4.0, I still get segfault when
running javac --version.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1129571
Title:
libreoffice armhf FTBFS
Status in Q
From: Peter Crosthwaite
commits 49b4c31efcce45ab714f286f14fa5d5173f9069d and
2de68a4900ef6eb67380b0c128abfe1976bc66e8 reworked the implementation of adc_CC
and sub_CC. The new implementations (on the TCG_TARGET_HAS_add2_i32 code path)
are incorrect. The new logic is:
CF:NF = 0:A +/- 0:CF
CF:NF =
On 25 February 2013 19:41, Richard Henderson wrote:
> V2->V3:
> Feedback from Peter Maydell: share code between adc_CC and sbc_CC.
>
> V1->V2:
> Dangit, that's what trying to be speedy gets you, failing to make
> all of the changes you wrote in the comment. This time actually
> fix the su
On 25 February 2013 19:01, Richard Henderson wrote:
> While ~T0+T1+CF = T1-T0+CF-1 is true for the low 32-bits,
> it does not produce the correct carry-out to bit 33. Do
> exactly what the manual says.
>
> Cc: Alexander Graf
> Signed-off-by: Richard Henderson
Not a PPC expert but this looks li
On 25 February 2013 19:41, Richard Henderson wrote:
> While T0+~T1+CF = T0-T1+CF-1 is true for the low 32-bits,
> it does not produce the correct carry-out to bit 33. Do
> exactly what the manual says.
>
> Using the ~T1 makes the add and subtract code paths nearly
> identical, so have sbc_CC use
On 25 February 2013 19:41, Richard Henderson wrote:
> From: Peter Crosthwaite
>
> commits 49b4c31efcce45ab714f286f14fa5d5173f9069d and
> 2de68a4900ef6eb67380b0c128abfe1976bc66e8 reworked the implementation of adc_CC
> and sub_CC. The new implementations (on the TCG_TARGET_HAS_add2_i32 code path)
V2->V3:
Feedback from Peter Maydell: share code between adc_CC and sbc_CC.
V1->V2:
Dangit, that's what trying to be speedy gets you, failing to make
all of the changes you wrote in the comment. This time actually
fix the sub2 to add2 like I intended, not just the not portion.
The patch s
On Mon, Feb 25, 2013 at 8:01 PM, Richard Henderson wrote:
> V1->V2:
> Dangit, that's what trying to be speedy gets you, failing to make
> all of the changes you wrote in the comment. This time actually
> fix the sub2 to add2 like I intended, not just the not portion.
>
> The patch set is re
From: Peter Crosthwaite
commits 49b4c31efcce45ab714f286f14fa5d5173f9069d and
2de68a4900ef6eb67380b0c128abfe1976bc66e8 reworked the implementation of adc_CC
and sub_CC. The new implementations (on the TCG_TARGET_HAS_add2_i32 code path)
are incorrect. The new logic is:
CF:NF = 0:A +/- 0:CF
CF:NF =
Enable ARMCPUInfo to specify a custom class_init functions.
Introduce arm_v7m_class_init() and use it for "cortex-m3" model.
Instead of forwarding from arm_cpu_do_interrupt() to do_interrupt_v7m(),
override CPUClass::do_interrupt with arm_v7m_cpu_do_interrupt()
in arm_v7m_class_init().
Signed-off
While ~T0+T1+CF = T1-T0+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Cc: Alexander Graf
Signed-off-by: Richard Henderson
---
target-ppc/translate.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --
V1->V2:
Dangit, that's what trying to be speedy gets you, failing to make
all of the changes you wrote in the comment. This time actually
fix the sub2 to add2 like I intended, not just the not portion.
The patch set is re-pushed at
git://github.com/rth7680/qemu.git fix-carry
Please *r
While T0+~T1+CF = T0-T1+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Cc: Peter Maydell
Reported-by: Laurent Desnogues
Signed-off-by: Richard Henderson
---
target-arm/translate.c | 8
1 file changed, 4 insertio
The SysBus qdev initfn merely calls SysBusDeviceClass::init, so we can
replace it with a realizefn already. This avoids getting into any initfn
ambiguity with the upcoming Faraday EHCI implementation.
Rename internal usb_ehci_initfn() to usb_ehci_realize() to allow to
return Errors from common ini
I'm struggling with the code to understand the "duty and soul" of the
"qemu_cpu_is_self" function (@cpus.c), and I quite not get it.
I see that this function is called from some points. E.g., from
tcg_hangle_interrupt and run_on_cpu. Amongst others.
Sometimes, seems to me that this function duty
On 25 February 2013 18:30, Richard Henderson wrote:
> Reported by Laurent for ARM, I made the exact same mistake for PPC.
>
> The patch set is at
>
> git://github.com/rth7680/qemu.git fix-carry
>
> Please apply asap.
Still busted :-(
-- PMM
Reindent, add missing braces and drop/adjust whitespace.
Prepares for CPUArchState-to-CPUState field movements in
cpu_cris_handle_mmu_fault(), do_interruptv10() and do_interrupt().
The remaining functions were so minor that they can be fixed in one go.
Acked-by: Edgar E. Iglesias
Signed-off-by:
Move it to qom/cpu.h to avoid issues with include order.
Change pc_acpi_smi_interrupt() opaque to X86CPU.
Signed-off-by: Andreas Färber
---
cpus.c |2 +-
exec.c |2 +-
hw/alpha_typhoon.c | 10 --
hw/apic.c| 21 +++
Stefan Hajnoczi wrote on wrote on 25/02/2013 02:50:56
PM:
> > However, I am concerned dataplane may not solve the scalability
> > problem because QEMU will be still running 1 thread
> > per VCPU and 1 per virtual device to handle I/O for each VM.
> > Assuming we run N VMs with 1 VCPU and 1 virt
Move it to qom/cpu.c to avoid build failures depending on include order
of cpu-qom.h and exec/cpu-all.h.
Change opaques of various ..._irq_handler() functions to the
appropriate CPU type to facilitate using cpu_reset_interrupt().
Fix Coding Style issues while at it (missing braces, indentation).
Instead of forwarding from cris_cpu_do_interrupt() to do_interruptv10(),
override CPUClass::do_interrupt with crisv10_cpu_do_interrupt() in the
newly introduced class_init functions.
Signed-off-by: Andreas Färber
---
target-cris/cpu-qom.h |1 +
target-cris/cpu.c |8
target-c
On 25 February 2013 18:45, Andreas Färber wrote:
> Enable ARMCPUInfo to specify a custom class_init functions.
> Introduce arm_v7m_class_init() and use it for "cortex-m3" model.
>
> Instead of forwarding from arm_cpu_do_interrupt() to do_interrupt_v7m(),
> override CPUClass::do_interrupt with arm_
Hello,
Rebased on my CPU VMState series v3, this series proceeds with moving fields
from CPU_COMMON / CPU*State to CPUState.
Thereby v2 doesn't need to drop x86 CPU version 5 VMState support.
v2 also QOM'ifies CRISv10 do_interrupt support.
Available for testing at:
git://github.com/afaerber/qemu
This removes a global per-target function and thus takes us one step
closer to compiling multiple targets into one executable.
It will also allow to override the interrupt handling for certain CPU
families.
Signed-off-by: Andreas Färber
---
cpu-exec.c | 36 +++
From: Marc-André Lureau
Compile and link with version.lo
Signed-off-by: Marc-André Lureau
---
Makefile | 8 ++--
rules.mak | 3 ++-
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/Makefile b/Makefile
index 2262410..5f0ded1 100644
--- a/Makefile
+++ b/Makefile
@@ -148,11 +14
From: Marc-André Lureau
It is needed to give that flag to the linker as well, but latest
libtool 2.4.2 still swallows that argument, so let's pass it with
libtool -Wc argument.
qemu-1.4.0/stubs/arch-query-cpu-def.c:6: undefined reference to
`__stack_chk_guard'
Signed-off-by: Marc-André Lureau
While T0+~T1+CF = T0-T1+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Cc: Peter Maydell
Reported-by: Laurent Desnogues
Signed-off-by: Richard Henderson
---
target-arm/translate.c | 8
1 file changed, 4 insertio
From: Peter Crosthwaite
commits 49b4c31efcce45ab714f286f14fa5d5173f9069d and
2de68a4900ef6eb67380b0c128abfe1976bc66e8 reworked the implementation of adc_CC
and sub_CC. The new implementations (on the TCG_TARGET_HAS_add2_i32 code path)
are incorrect. The new logic is:
CF:NF = 0:A +/- 0:CF
CF:NF =
This avoids adding a duplicate stub for CONFIG_USER_ONLY.
Suggested-by: Eduardo Habkost
Reviewed-by: Eduardo Habkost
Reviewed-by: Juan Quintela
Signed-off-by: Andreas Färber
---
include/migration/vmstate.h | 12 ++--
savevm.c|7 ---
2 Dateien geändert, 10
This setter avoids redefining each VMStateDescription value to
vmstate_dummy by not referencing the value for CONFIG_USER_ONLY.
Suggested-by: Juan Quintela
Signed-off-by: Andreas Färber
---
include/qom/cpu.h | 17 +
1 Datei geändert, 17 Zeilen hinzugefügt(+)
diff --git a/incl
While ~T0+T1+CF = T1-T0+CF-1 is true for the low 32-bits,
it does not produce the correct carry-out to bit 33. Do
exactly what the manual says.
Cc: Alexander Graf
Signed-off-by: Richard Henderson
---
target-ppc/translate.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --
Reported by Laurent for ARM, I made the exact same mistake for PPC.
The patch set is at
git://github.com/rth7680/qemu.git fix-carry
Please apply asap.
r~
Peter Crosthwaite (1):
arm/translate.c: Fix adc_CC/sbc_CC implementation
Richard Henderson (2):
target-arm: Fix sbc_CC carry
ta
SYS_CFG_DVIMODE allows the guest to select whether the
output DVI signal is VGA, SVGA, XGA, SGA or UXGA. Since
this makes no difference to QEMU, implement writes as a
no-op so Linux doesn't complain.
Signed-off-by: Peter Maydell
---
hw/arm_sysctl.c |8
1 file changed, 8 insertions(+
Am 22.02.2013 16:27, schrieb Andreas Färber:
> Am 22.02.2013 15:14, schrieb Juan Quintela:
>> Eduardo Habkost wrote:
>>> On Fri, Feb 22, 2013 at 02:22:43PM +0100, Juan Quintela wrote:
Andreas Färber wrote:
> Commit b758aca1f6cdb175634812b79f5560c36c902d00 (target-alpha: Enable
> the
Add a vmstate_lm32_cpu referencing the previous VMStateDescription as a
sub-struct and hook it up to CPUClass::vmsd. Drop cpu_{save,load}().
Signed-off-by: Andreas Färber
---
target-lm32/cpu-qom.h |4
target-lm32/cpu.c |2 ++
target-lm32/cpu.h |2 --
target-lm32/machine.
On 25 February 2013 17:15, Laurent Desnogues
wrote:
> I'm afraid this fix is not enough
I've confirmed with my risu test tool that sbcs/adcs are indeed
broken even with this patch applied. Patterns used:
ADC_imm A1 cond:4 0010101 s:1 rn:4 rd:4 imm:12
ADC_reg A1 cond:4 101 s:1 rn:4 rd:4 imm:5
Hello,
In response to patches from Juan [1], this series implements a declarative way
for CPUs to register their CPU-specific VMStateDescription.
v3 dropped alpha and openrisc, leaving only x86 as prereq for my qom-cpu-9 and
lm32 as proof of concept for leave-CPUArchState-untouched-if-not-needed.
Expose vmstate_cpu as vmstate_x86_cpu and hook it up to CPUClass::vmsd.
Adapt opaques and VMState fields to X86CPU. Drop cpu_{save,load}().
Signed-off-by: Andreas Färber
---
target-i386/cpu-qom.h |4 +
target-i386/cpu.c |2 +
target-i386/cpu.h |2 -
target-i386/machine.c | 2
Reviewed-by: Juan Quintela
Signed-off-by: Andreas Färber
---
include/migration/vmstate.h |4
stubs/vmstate.c |2 ++
2 Dateien geändert, 6 Zeilen hinzugefügt(+)
diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
index 6d50f6e..214a8e9 100644
--- a/inc
In comparison to DeviceClass::vmsd, CPU VMState is split in two,
"cpu_common" and "cpu", and uses cpu_index as instance_id instead of -1.
Therefore add a CPU-specific CPUClass::vmsd field.
Unlike the legacy CPUArchState registration, rather register CPUState.
Signed-off-by: Juan Quintela
Signed-
From: Peter Lieven
XBZRLE encoded migration introduced a MRU page cache
meachnism. Unfortunately, cached items where never freed in
case of a collision in the page cache on cache_insert().
This lead to out of memory conditions during XBZRLE migration
if the page cache was small and there where a
Pass voltage sensor properties to the sysctl device. Since
these are daughterboard specific, we specify them via the
VEDBoardInfo structure.
Signed-off-by: Peter Maydell
Message-id: 1359985476-29380-9-git-send-email-peter.mayd...@linaro.org
---
hw/vexpress.c | 30 ++
Add support for declaring array properties for qdev devices.
These work by defining an initial static property 'len-arrayname'
which the user of the device should set to the desired size
of the array. When this property is set, memory is allocated
for the array elements, and dynamic properties "arr
Il 25/02/2013 18:56, Marc-André Lureau ha scritto:
> vscclient needs to call socket_init() for portability.
> Moving to osdep.c since it has no internal dependency.
>
> Signed-off-by: Marc-André Lureau
> ---
> util/osdep.c| 23 +++
> util/qemu-sockets.c | 24 -
1 - 100 of 319 matches
Mail list logo
