hi
I have added support for MIPS64 user mode emulation in QEMU and email git
patch to the qemu-devel mailing list
but I got no any response yet. My Patch mail has the following subject line
MIPS64 user mode emulation Patch
please verify that this patch mail is not neglected or guide me towards the
On 03/28/11 18:11, Alon Levy wrote:
This patchset adds three new devices, usb-ccid, ccid-card-passthru and
ccid-card-emulated, providing a CCID bus, a simple passthru protocol
implementing card requiring a client, and a standalone emulated card.
It also introduces a new directory libcaccard
On Mon, Mar 28, 2011 at 08:13:04AM -0500, Anthony Liguori wrote:
On 03/27/2011 08:19 PM, David Gibson wrote:
We should pull in SLOF via a git submodule. That ensures we ship
the source code along with the binary.
Um, ok. Do I need to do anything about this?
We should introduce SLOF as one
Ryan Harper ry...@us.ibm.com writes:
* Markus Armbruster arm...@redhat.com [2011-03-24 07:27]:
Whoops, almost missed this. Best to cc: me to avoid that.
It was sent directly to you:
Sender: qemu-devel-bounces+ryanh=us.ibm@nongnu.org
From: Ryan Harper ry...@us.ibm.com
Subject:
On 03/28/2011 07:21 PM, Blue Swirl wrote:
What's the distinction between vm state and machine state?
VM state should be invisible (except for PV devices).
Got it. That's why I called it emulator state (a bit generic, but
more precise than vm state: vm_clock for example is
From: Jes Sorensen jes.soren...@redhat.com
This adds the basic infrastructure for supporting progress output
on the command line, as well as progress support for qemu-img commands
'rebase' and 'convert'.
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
---
Makefile.objs|2 +-
On 28.03.2011, at 17:40, Peter Maydell wrote:
On 24 March 2011 15:58, Alexander Graf ag...@suse.de wrote:
diff --git a/target-s390x/translate.c b/target-s390x/translate.c
+typedef struct DisasContext DisasContext;
+struct DisasContext {
+uint64_t pc;
+int is_jmp;
+enum cc_op
Hi,
First, do you have some instructions on howto build Octeon usermode
64bit binaries. Second, I think we would prefer that the patch was split
to smaller patches. At least the target-mips changes should be a separate
patch.
Some more comments included inline between the code.
On Sat, Mar 26,
Since you have to respin anyway, would you mind limiting commit message
line length to 70-75 characters? Thanks.
On 28.03.2011, at 19:55, Peter Maydell wrote:
On 28 March 2011 18:23, Alexander Graf ag...@suse.de wrote:
On 03/24/2011 06:29 PM, Peter Maydell wrote:
+/* condition codes for binary FP ops */
+static uint32_t set_cc_f32(float32 v1, float32 v2)
+{
+if (float32_is_any_nan(v1) ||
On 28.03.2011, at 20:02, Anthony Liguori wrote:
On 03/28/2011 12:42 PM, Blue Swirl wrote:
On Mon, Mar 28, 2011 at 4:16 PM, Anthony Liguorianth...@codemonkey.ws
wrote:
On 03/28/2011 04:03 AM, Alexander Graf wrote:
Um, ok. Do I need to do anything about this?
I'm also not sure this is too
On 28.03.2011, at 21:52, Aurelien Jarno wrote:
On Mon, Mar 28, 2011 at 01:50:40PM -0500, Anthony Liguori wrote:
On 03/28/2011 01:24 PM, Aurelien Jarno wrote:
On Mon, Mar 28, 2011 at 01:02:45PM -0500, Anthony Liguori wrote:
On 03/28/2011 12:42 PM, Blue Swirl wrote:
On Mon, Mar 28, 2011 at
On 29 March 2011 09:55, Alexander Graf ag...@suse.de wrote:
On 28.03.2011, at 17:40, Peter Maydell wrote:
On 24 March 2011 15:58, Alexander Graf ag...@suse.de wrote:
diff --git a/target-s390x/translate.c b/target-s390x/translate.c
+ case 0x4: /* LMG R1,R3,D2(B2) [RSE] */
+
On 03/21/2011 09:24 AM, Paolo Bonzini wrote:
On 03/09/2011 06:21 PM, Paolo Bonzini wrote:
QEMU has a sigchld handler that reaps any child process. -smb is the
only user of it and, in fact, QEMU inherited it from slirp. However,
this handler causes 'exec' based migration to randomly return
On 29.03.2011, at 11:17, Peter Maydell wrote:
On 29 March 2011 09:55, Alexander Graf ag...@suse.de wrote:
On 28.03.2011, at 17:40, Peter Maydell wrote:
On 24 March 2011 15:58, Alexander Graf ag...@suse.de wrote:
diff --git a/target-s390x/translate.c b/target-s390x/translate.c
+case
Public bug reported:
It's not possible to pass more than 6 disks to a guest since qemu-kvm-0.13
(also tested with 0.14).
If I pass more than 6 disks (as shown below) the machine complains that their
is no bootable disk,
The problem occurs with virtio and without virtio.
eg.
On 28.03.2011, at 16:54, Peter Maydell wrote:
On 24 March 2011 15:58, Alexander Graf ag...@suse.de wrote:
diff --git a/target-s390x/cpu.h b/target-s390x/cpu.h
Minor nits only.
-FPReg fregs[16]; /* FP registers */
+CPU_DoubleU fregs[16]; /* FP registers */
These changes mean
On (Mon) 28 Mar 2011 [23:14:16], Michael S. Tsirkin wrote:
When guest does something illegal, such as
programming invalid index values in the virtio
device, qemu currently tends to crash.
With virtio, a better idea is to log an error,
and set status to FAIL which stops the device.
Add an
On 29 March 2011 10:25, Alexander Graf ag...@suse.de wrote:
On 29.03.2011, at 11:17, Peter Maydell wrote:
On 29 March 2011 09:55, Alexander Graf ag...@suse.de wrote:
On 28.03.2011, at 17:40, Peter Maydell wrote:
Doesn't this take you over MAX_OP_PER_INSTR for some cases?
I haven't
On 29.03.2011, at 11:56, Peter Maydell wrote:
On 29 March 2011 10:25, Alexander Graf ag...@suse.de wrote:
On 29.03.2011, at 11:17, Peter Maydell wrote:
On 29 March 2011 09:55, Alexander Graf ag...@suse.de wrote:
On 28.03.2011, at 17:40, Peter Maydell wrote:
Doesn't this take you over
On Tue, 29 Mar 2011, Feiran Zheng wrote:
Bug fix: routines 'ioreq_runio_qemu_sync' and 'ioreq_runio_qemu_aio'
won't call 'ioreq_unmap' or 'ioreq_finish' on errors, leaving ioreq in
the blkdev-inflight list and a leak.
Acked-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
Can QEMU run on QNX ?
My machine is
Cpu - arm11
Os - qnx6.5
Does QEMU support my machine ?
Thanks.
Is there a web viewer for the git repository?
The download page links to http://git.qemu.org/qemu.git but that's 404,
and http://git.qemu.org says I don't have permission to access /.
Rob
On Mon, Mar 28, 2011 at 10:14 PM, Michael S. Tsirkin m...@redhat.com wrote:
vhost used cpu_physical_memory_map to get the
virtual address for the ring, however,
this will exit on an illegal RAM address.
Since the addresses are guest-controlled, we
shouldn't do that.
Switch to our own
Hi,
I am using ARM realview cortex a9 board with qemu-0.14.0
It uses lan9118 network interface. I am connecting to the outside network by
creating a bridge on my host's eth0 interface.
I am facing some network glitch while transferring a large file. If I
transfer a small file between my guest and
Am 29.03.2011 12:48, schrieb Stefano Stabellini:
On Tue, 29 Mar 2011, Feiran Zheng wrote:
Bug fix: routines 'ioreq_runio_qemu_sync' and 'ioreq_runio_qemu_aio'
won't call 'ioreq_unmap' or 'ioreq_finish' on errors, leaving ioreq in
the blkdev-inflight list and a leak.
Acked-by: Stefano
Paolo Bonzini pbonz...@redhat.com writes:
QEMU has a sigchld handler that reaps any child process. -smb is the
only user of it and, in fact, QEMU inherited it from slirp. However,
this handler causes 'exec' based migration to randomly return 'status:
failed' in the monitor. This happens
See above mail, sent by Anthony yesterday :
We've been having problems on qemu.org all day. Initially, it was
due
to a combination of a small DoS attack (not uncommon unfortunately).
Later, the issue was observed when a crawler that was ignoring
robots.txt started indexing git.qemu.org.
This patchset fixes the Sheepodg AIO problems pointed out in:
http://lists.gnu.org/archive/html/qemu-devel/2011-02/msg02495.html
http://lists.gnu.org/archive/html/qemu-devel/2011-02/msg02474.html
Thanks,
Kazutaka
MORITA Kazutaka (3):
sheepdog: make send/recv operations non-blocking
We cannot access the buffer of the canceled I/O request because its
AIOCB callback is already called and the buffer is not valid.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
---
block/sheepdog.c | 12 ++--
1 files changed, 10 insertions(+), 2 deletions(-)
diff --git
We can cancel I/O requests safely if they are not sent to the servers.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
---
block/sheepdog.c | 37 +
1 files changed, 37 insertions(+), 0 deletions(-)
diff --git a/block/sheepdog.c
This patch avoids retrying send/recv in AIO path when the sheepdog
connection is not ready for the operation.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
---
block/sheepdog.c | 417 +-
1 files changed, 289 insertions(+), 128
On 03/29/2011 01:52 PM, Markus Armbruster wrote:
To avoid this, register the pids in a list and, on SIGCHLD, set up a
bottom-half that would go through the pids and reap them.
Signal handler now waitpid()s only for registered children, so it can't
steal zombies anymore.
Exactly.
Since I'm
On Fri, Mar 18, 2011 at 01:19:15PM +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
This allows to override the interrupt handling of QEMU in system mode.
KVM will make use of it to set a specialized handler.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
cpu-all.h
Please, send in any agenda items you are interested in covering.
Later, Juan.
On 03/29/2011 06:58 AM, Frédéric Grelot wrote:
See above mail, sent by Anthony yesterday :
My plan is to upgrade cgit later today FWIW. If anyone has experience
with other git front ends, I'd appreciate hearing about it. Since
qemu.org has pretty high traffic, I wanted something that
The ivshmem depends on PCI and KVM, not only KVM. Reflect this
in the Makefile, so we don't get build errors on s390x.
Signed-off-by: Alexander Graf ag...@suse.de
CC: Cam Macdonell c...@cs.ualberta.ca
CC: Juan Quintela quint...@redhat.com
---
Makefile.target |8 +++-
1 files changed, 7
From: Ulrich Hecht u...@suse.de
This patch enables the instruction disassembler when using an
S390x target.
Signed-off-by: Ulrich Hecht u...@suse.de
---
disas.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/disas.c b/disas.c
index c76f36f..17b4ce4 100644
---
The KVM interrupt injection path is non-generic for now. So we need to push
knowledge of how to inject a device interrupt using KVM into the actual device
code.
Signed-off-by: Alexander Graf ag...@suse.de
---
hw/s390-virtio-bus.c | 10 --
1 files changed, 8 insertions(+), 2
We have two different virtio buses: pci and s390. The abstraction path
taken in qemu is to have generic aliases for each device type in the
architecture specific qdev devices.
So let's make use of these aliases whenever we can and define them
whenever we can.
Signed-off-by: Alexander Graf
From: Ulrich Hecht u...@suse.de
S390x user emulation can do nptl. Reflect this in the configure script.
Signed-off-by: Ulrich Hecht u...@suse.de
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 5a5827f..978fd1f 100755
---
We're now finally emulating an s390x CPU, so we can move quite some logic
from the kvm code out into generic CPU code.
This patch does this and adjusts the interfaces according to what the code
around now expects to be able to call.
Signed-off-by: Alexander Graf ag...@suse.de
---
For emulation (and migration) we need to know about the guest's storage keys.
These are separate from actual RAM contents, so we need to allocate them in
parallel to RAM.
While touching the file, this patch also adjusts the hypercall function
to a new syntax that aligns better with tcg emulated
Commit 6b331efb733a0f913ddc0b7762a1307dec304061 broke the s390 proxy version
of virtio-serial by only taking its PCI brother into account.
So let's adjust s390-virtio-serial the same way as its PCI counterpart, making
it compile and work again.
Signed-off-by: Alexander Graf ag...@suse.de
CC:
During Jan's rework of the generic KVM layer, he added some more error checks
and actually aborted if something went wrong. Unfortunately, one of the s390
internal error codes slipped through, aborting the VM without needing to.
This patch fixes booting of S390x virtual machines in KVM.
From: Ulrich Hecht u...@suse.de
Quite a number of syscalls are only defined on systems with USE_UID16
defined; this patch defines them on other systems as well.
Fixes a large number of uid/gid-related testcases on the s390x target
(and most likely on other targets as well)
Signed-off-by: Ulrich
We have successfully lazilized cc computation, so we need to manually
trigger its calculation when gdb wants to fetch it. We also changed the
variable name, so writing it writes into a different field now.
Signed-off-by: Alexander Graf ag...@suse.de
---
gdbstub.c |8 ++--
1 files
Since kernel 2.6.38, smsc911x driver writes to VLAN1 registger.
Signed-off-by: Atsushi Nemoto an...@mba.ocn.ne.jp
---
hw/lan9118.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/hw/lan9118.c b/hw/lan9118.c
index af6949f..62aead3 100644
--- a/hw/lan9118.c
+++
From: Ulrich Hecht u...@suse.de
S390x uses the QuadU type, so let's enable it.
Signed-off-by: Ulrich Hecht u...@suse.de
---
cpu-all.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/cpu-all.h b/cpu-all.h
index 4f4631d..4cc445f 100644
--- a/cpu-all.h
+++ b/cpu-all.h
@@
This patch adds some code paths for running s390x guest OSs without the
need for KVM.
Signed-off-by: Alexander Graf ag...@suse.de
---
cpu-exec.c |8
target-s390x/exec.h | 20
2 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/cpu-exec.c
We need to add some more logic to the CPU description to leverage emulation
of an s390x CPU. This patch adds all the required helpers, fields in CPUState
and constant definitions required for user and system emulation.
Signed-off-by: Alexander Graf ag...@suse.de
---
v1 - v2:
- remove FPReg
We've had support for running s390x guests with KVM for a
while now. This patch set also enables support for running
s390x guests in system as well as linux-user mode in emulation!
Within this scope, I again want to stress that this is _not_
supposed to replace Hercules - the s390 emulator - in
When running system emulation, we need to transverse through the MMU and
deliver interrupts according to the specification.
This patch implements those two pieces and in addition adjusts the CPU
initialization code to account for the new fields in CPUState.
Signed-off-by: Alexander Graf
This patch enables building of s390x-softmmu and s390x-linux-user
targets by default.
Signed-off-by: Alexander Graf ag...@suse.de
---
configure|2 ++
default-configs/s390x-linux-user.mak |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
create mode
Fedora 14
- We have 91 open bugs, 10 of which have fixes in awaiting updates.
- 7 bugs have been closed in the last week
Fedora 15
- Upcoming Deadlines:
2011-03-29 Software Translation Deadline
2011-04-05 Beta Change Deadline Features 100% Complete
2011-04-19 Beta Release
2011-05-09
On 03/09/2011 11:21 AM, Paolo Bonzini wrote:
QEMU has a sigchld handler that reaps any child process. -smb is the
only user of it and, in fact, QEMU inherited it from slirp. However,
this handler causes 'exec' based migration to randomly return 'status:
failed' in the monitor. This happens
Reimplement the list of QEMUMachine structures so that we don't keep the
'next' pointer inside the QEMUMachine struct itself. This allows us to
accept a const struct pointer in qemu_register_machine. The few places
in vl.c which were implicitly assuming that QEMUMachine structs were
writable have
From: Ulrich Hecht u...@suse.de
This patch adds support for running s390x binaries in the linux-user emulation
code.
Signed-off-by: Ulrich Hecht u...@suse.de
Signed-off-by: Alexander Graf ag...@suse.de
---
v1 - v2:
- always set 64bit flag for s390x binaries in elf loader
- remove
Allow boards to specify their maximum RAM size in the QEMUMachine struct.
This allows us to provide a useful diagnostic if the user tries to specify
a RAM size that the board cannot support.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/boards.h |1 +
vl.c| 16
Now that qemu_register_machine() accepts a const QEMUMachine *, we can
mark all the static QEMUMachine structure definitions for boards as
being const.
This patch was mostly automatically generated via:
sed -i -e 's/^static QEMUMachine /static const QEMUMachine /' hw/*.c
and then checked for
Specify the maximum memory permitted for the various ARM devboard
models (integratorcp, realview-eb, realview-eb-mpcore, realview-pb-a8,
realview-pbx-a9, versatilepb, versatileab). This means we now handle
attempts to specify too much RAM gracefully rather than causing
the guest to crash in an
Use the max_ram field in QEMUMachine to indicate maximum memory,
rather than a field in the sun4*_hwdef structure. This allows us
to use the vl.c check on RAM specifications rather than having to
code our own.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/sun4m.c | 42
This primary aim of this patchset is to add a new 'max_ram' field to the
QEMUMachine structure so that a board model can specify the maximum RAM it
will accept. We can then produce a friendly diagnostic message when the
user tries to start qemu with a '-m' option asking for more RAM than that.
Combine the per-machine QEMUMachine struct into the per-machine
sun4*_hwdef struct. This requires some moving around of init functions
to avoid forward references.
The motivation is to allow the init functions to get at the
QEMUMachine struct for the board, so we can use its max_ram field
rather
Juan Quintela quint...@redhat.com wrote:
Please, send in any agenda items you are interested in covering.
Later, Juan.
As there is no topic for the agenda (I asked for topics too late), call
is canceled.
Later, Juan.
Tidy up the repetitive board init functions (which are all the same
apart from which hwdef struct they pass in). This also lets us add
an assertion that the hwdef points to the init function which uses
that hwdef, rather than some other one.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
On (Tue) 29 Mar 2011 [15:29:31], Alexander Graf wrote:
Commit 6b331efb733a0f913ddc0b7762a1307dec304061 broke the s390 proxy version
of virtio-serial by only taking its PCI brother into account.
So let's adjust s390-virtio-serial the same way as its PCI counterpart, making
it compile and work
* Markus Armbruster arm...@redhat.com [2011-03-29 02:44]:
Ryan Harper ry...@us.ibm.com writes:
When removing a drive from the host-side via drive_del we currently have the
following path:
drive_del
qemu_aio_flush()
bdrv_close()// zaps bs-drv, which makes any subsequent I/O get
* Markus Armbruster arm...@redhat.com [2011-03-29 04:06]:
Since you have to respin anyway, would you mind limiting commit message
line length to 70-75 characters? Thanks.
yep
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ry...@us.ibm.com
Instead of calling flush_queued_data when unthrottling, schedule
a bh. That way we can return immediately to the caller, and the
flush uses the same call path as a have_data for callbackee.
migration: since version 2 of the migration protocol we unthrottle
if there is data. So we don't need to
On 03/29/2011 06:29 AM, Alexander Graf wrote:
+if (src == dest) {
+memset((void*)dest, 0, l + 1);
+return 0;
+}
This should be g2h(dest), surely.
r~
On 03/29/2011 06:13 PM, Richard Henderson wrote:
On 03/29/2011 06:29 AM, Alexander Graf wrote:
+if (src == dest) {
+memset((void*)dest, 0, l + 1);
+return 0;
+}
This should be g2h(dest), surely.
Ah, nice. Didn't know about that one :). Very useful indeed.
Alex
Hello,
On 3/27/11, Peter Maydell peter.mayd...@linaro.org wrote:
I've just gone through this distinguishing v5 sublevels.
I've also gone back and looked up an older ARM ARM for any v5 vs
v5T differences, and it looks like the only difference really is
whether Thumb mode works: the ARM
Basic implementation of DEC/Intel SA-1100/SA-1110 chips emulation.
Implemented:
- IRQs
- GPIO
- PPC
- RTC
- UARTs (no IrDA/etc.)
- OST reused from pxa25x
Everything else is TODO (esp. PM/idle/sleep!) - see the todo in the
hw/strongarm.c
V2:
* removed all strongarm variants except latest
Add very basic implementation of collie PDA emulation. The system lacks
LoCoMo and graphics/sound emulation. Linux kernel boots up to mounting
rootfs (theoretically it can be provided in pflash images).
Signed-off-by: Dmitry Eremin-Solenikov dbarysh...@gmail.com
---
Makefile.target |1 +
Currently target-arm/ assumes at least ARMv5 core. Add support for
handling also ARMv4/ARMv4T. This changes the following instructions:
BX(v4T and later)
BKPT, BLX, CDP2, CLZ, LDC2, LDRD, MCRR, MCRR2, MRRC, MCRR, MRC2, MRRC,
MRRC2, PLD QADD, QDADD, QDSUB, QSUB, STRD, SMLAxy, SMLALxy, SMLAWxy,
On Tue, Mar 29, 2011 at 11:14 AM, Paolo Bonzini pbonz...@redhat.com wrote:
On 03/28/2011 07:21 PM, Blue Swirl wrote:
What's the distinction between vm state and machine state?
VM state should be invisible (except for PV devices).
Got it. That's why I called it emulator state (a bit
On 29 March 2011 17:58, Dmitry Eremin-Solenikov dbarysh...@gmail.com wrote:
Looks good, nearly there I think.
@@ -7172,10 +7191,11 @@ static void disas_arm_insn(CPUState * env,
DisasContext *s)
}
if (insn (1 20)) {
/* Complete the load. */
-
From: Anthony PERARD anthony.per...@citrix.com
Hi all,
Here is the few change made since the v11:
- All objects built for each target are now build only for i386 targets.
- The compatibility macros have been replaced by static inline functions.
- xen_platform_init replaced by a call to
From: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf ag...@suse.de
---
Makefile.target |9 +
hw/xen.h| 13 +
vl.c|2 ++
xen-all.c | 23 +++
From: Steven Smith ssm...@xensource.com
Introduce a new emulated PCI device, specific to fully virtualized Xen
guests. The device is necessary for PV on HVM drivers to work.
Signed-off-by: Steven Smith ssm...@xensource.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by:
From: Anthony PERARD anthony.per...@citrix.com
xen_domainbuild and xen_machine_pv are built only for i386 targets.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
Makefile.target |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Makefile.target
From: Anthony PERARD anthony.per...@citrix.com
This patch updates the libxenctrl calls in Qemu to use the new interface,
otherwise Qemu wouldn't be able to build against new versions of the
library.
We check libxenctrl version in configure, from Xen 3.3.0 to Xen
unstable.
Signed-off-by: Anthony
From: Anthony PERARD anthony.per...@citrix.com
This patch introduces Xen specific call in piix_pci.
The specific part for Xen is in write_config, set_irq and get_pirq.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
From: Jun Nakajima jun.nakaj...@intel.com
On IA32 host or IA32 PAE host, at present, generally, we can't create
an HVM guest with more than 2G memory, because generally it's almost
impossible for Qemu to find a large enough and consecutive virtual
address space to map an HVM guest's whole
From: Anthony PERARD anthony.per...@citrix.com
Introduce the Xen FV (Fully Virtualized) machine to Qemu, some more Xen
specific call will be added in further patches.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
hw/pc.c | 19 +--
hw/pc_piix.c | 17
From: Anthony PERARD anthony.per...@citrix.com
Every set_irq call makes a Xen hypercall.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
---
hw/pc_piix.c |8 ++--
hw/xen.h |2 ++
xen-all.c| 12
From: Anthony PERARD anthony.per...@citrix.com
This tells to the xen management tool that the machine can begin run.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf ag...@suse.de
---
xen-all.c | 23 +++
1 files changed, 23 insertions(+), 0
From: Anthony PERARD anthony.per...@citrix.com
This function allows to unlock a ram_ptr give by qemu_get_ram_ptr. After
a call to qemu_put_ram_ptr, the pointer may be unmap from QEMU when
used with Xen.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf
From: Anthony PERARD anthony.per...@citrix.com
With MapCache, we can handle a 64b target, even with a 32b host/qemu.
So, we need to have target_phys_addr_t to 64bits.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Acked-by: Alexander Graf ag...@suse.de
---
configure |1 +
1 files
From: Arun Sharma arun.sha...@intel.com
Open and bind event channels; map ioreq and buffered ioreq rings.
Signed-off-by: Arun Sharma arun.sha...@intel.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini stefano.stabell...@eu.citrix.com
Acked-by:
From: John Baboval john.babo...@virtualcomputer.com
Adds a cap to the number of map cache entries. This prevents the map
cache from overwhelming system memory.
I also removed the bitmap macros and #included bitmap.h instead.
Signed-off-By: John Baboval john.babo...@virtualcomputer.com
From: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
hw/pc_piix.c |6 +-
hw/xen.h |1 +
xen-all.c|9 +
xen-stub.c |4
4 files changed, 19 insertions(+), 1 deletions(-)
diff --git a/hw/pc_piix.c
From: Anthony PERARD anthony.per...@citrix.com
Introduce two functions qemu_shutdown_requested_get and
qemu_reset_requested_get to get the value of shutdown/reset_requested
without reset it.
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
Signed-off-by: Stefano Stabellini
From: John Baboval john.babo...@virtualcomputer.com
Prevent a deadlock caused by leaving a map cache bucket locked by the
preceding qemu_get_ram_ptr() call.
Signed-off-By: John Baboval john.babo...@virtualcomputer.com
Signed-off-by: Anthony PERARD anthony.per...@citrix.com
---
hw/pci.c |2
The block layer caches the device size to avoid doing lseek(fd, 0,
SEEK_END) every time this value is needed. For removable media the
device size becomes stale if a new medium is inserted. This patch
simply prevents device size caching for removable media.
A smarter solution is to update the
This patch series fixes two Linux host CD-ROM pass-through bugs in QEMU.
After applying these patches it is possible to pass-through a Linux host CD-ROM
completely. The guest can eject from software or the physical eject button can
be pressed on the drive. The guest can detect this and newly
Piggy-back on the guest CD-ROM polling to poll on the host. Open and
close the host CD-ROM file descriptor to ensure we read the new size and
not a stale size.
Two things are going on here:
1. If hald/udisks is not already polling CD-ROMs on the host then
re-opening the CD-ROM causes the
It can be handy to know when the guest locks/unlocks the CD-ROM tray.
This trace event makes that possible.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block.c |2 ++
trace-events |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/block.c
Hi,
Am 29.03.2011 um 08:49 schrieb Khansa Butt:
I have added support for MIPS64 user mode emulation in QEMU and
email git patch to the qemu-devel mailing list
but I got no any response yet. My Patch mail has the following
subject line
MIPS64 user mode emulation Patch
please verify that
1 - 100 of 108 matches
Mail list logo
