On 03/02/2013 01:38 AM, Eric Blake wrote:
On 03/01/2013 02:33 AM, Lei Li wrote:
Signed-off-by: Lei Li li...@linux.vnet.ibm.com
---
qga/commands-posix.c | 55
qga/qapi-schema.json | 27 ++
2 files changed, 82
On Sun, Mar 3, 2013 at 10:35 AM, Abel Gordon ab...@il.ibm.com wrote:
Stefan Hajnoczi stefa...@gmail.com wrote on 01/03/2013 12:54:54 PM:
On Thu, Feb 28, 2013 at 08:20:08PM +0200, Abel Gordon wrote:
Stefan Hajnoczi stefa...@gmail.com wrote on 28/02/2013 04:43:04 PM:
I think extending and
Hi All. The clock controller module in the Zynq platform has the ability to halt
and reset arbitrary devices, including the CPU. We use this feature to implement
SMP Linux - the kernel halts CPU1 then rewrites the vector table to the
secondary entry point and unhalts.
The clock controller however
Define APIs on the device level for halting and un-halting a device. The
semantic is the device freezes its state and does not respond to any form
of transaction.
The main intended use cases is to implement clock gating and power down. clock
gating is just a halt, whereas power down is a reset()
Set up the Device level halting API to halt cpus. This allows holders of a
pointer to the CPU to halt it from the TYPE_DEVICE abstraction. (i.e. they
can halt it even if they dont know its a CPU).
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
qom/cpu.c | 16
Hookup the CPU::reset function up as the Device::reset function. This allows
devices that abstract away the fact that the device is a CPU to reset it.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
qom/cpu.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
Example for a change pattern that could be applied to use the halting API rather
than directly modifying the CPU halted bit.
Untested RFC.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
---
hw/sun4m.c | 24
1 files changed, 12 insertions(+), 12
From: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
Added linux smp support for the xilinx zynq platform (2x cpus are supported)
Signed-off-by: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
---
Changed from v2:
macro defined the maximum number of CPUS
Changed from v1:
From: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
The SLCR needs to be able to reset the CPUs, so link the CPUs to the slcr.
Signed-off-by: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
---
Changed from v2:
Soften type of CPU to Device
Looped link creator
hw/xilinx_zynq.c
From: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
Implement the CPU reset and halt functions of the A9_CPU_RST_CTRL register
(offset 0x244).
Signed-off-by: Peter A. G. Crosthwaite peter.crosthwa...@petalogix.com
---
changed from v2:
used device halting API instead of talking to the
Phani Vadrevu pvadr...@gmail.com writes:
Hi list,
I am trying to write a device emulator for a Broadcom card. As
reference, I am looking at e1000.c code of 1.2.2 version. In that
code, there is this line: DEFINE_NIC_PROPERTIES( E1000State, conf);
Is there a definite structure for
On Sun, Mar 03, 2013 at 10:21:32AM -0700, Alex Williamson wrote:
Each PCI Bridge has a set of implied VGA regions that are enabled when
the VGA bit is set in the bridge control register. This allows VGA
devices behind bridges. Unfortunately with VGA Enable, which we
formerly allowed but
On Sun, Mar 03, 2013 at 10:21:20AM -0700, Alex Williamson wrote:
Bridges aren't the only thing that needs to know about VGA, any class
VGA device can register for VGA. This adds infrastructure to PCI to
allow devices to register VGA regions and incorporates the previous
PCI bridge only patch
The following changes since commit 806f352d3d6f7b326b0ab3a49c622b124459dc8d:
gen-icount.h: Rename gen_icount_start/end to gen_tb_start/end (2013-03-03
14:29:08 +)
are available in the git repository at:
git://github.com/stefanha/qemu.git block
for you to fetch changes up to
From: Mark Cave-Ayland mark.cave-ayl...@ilande.co.uk
Commit 07a7484e5d713f1eb7c1c37b18a8ab0d56d88875 accidentally introduced a bug
in the initialisation of the second macio DMA device which could cause some
DMA operations to segfault QEMU.
CC: Andreas Färber afaer...@suse.de
Signed-off-by: Mark
From: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Fix coding style in tcp_connect before the next patch.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
slirp/tcp_subr.c | 140
From: Christian Borntraeger borntrae...@de.ibm.com
virtio-blk registers a vmstate change handler. Unfortunately this
handler is not unregistered on unplug, leading to some random
crashes if the system is restarted, e.g. via virsh reboot.
Lets unregister the vmstate change handler if the device is
From: Paolo Bonzini pbonz...@redhat.com
During the review of the dataplane code, the EventPoll API morphed itself
(not concidentially) into something very very similar to an AioContext.
Thus, it is trivial to convert virtio-blk-dataplane to use AioContext,
and a first baby step towards letting
From: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
This uses the form host:port for the representation of the
sheepdog server to use inet_connect.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
block/sheepdog.c | 111
From: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
The URI syntax is consistent with the NBD and Gluster syntax. The
syntax is
sheepdog[+tcp]://[host:port]/vdiname[#snapid|#tag]
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
From: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
block/sheepdog.c | 11 +--
gdbstub.c | 5 ++---
include/qemu/sockets.h | 1 +
qemu-char.c
From: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
This patch adds support for a unix domain socket for a connection
between qemu and local sheepdog server. You can use the unix domain
socket with the following syntax:
$ qemu sheepdog+unix:///vdiname?socket=socket path[#snapid]
This patch series attempts to add time resync support
to qemu-ga by introducing qemu-ga commands guest-get-time
and guest-set-time.
Right now, when a guest is paused or migrated to a file
then loaded from that file, the guest OS has no idea that
there was a big gap in the time. Depending on how
Signed-off-by: Lei Li li...@linux.vnet.ibm.com
---
qga/commands-posix.c | 16
qga/qapi-schema.json | 13 +
2 files changed, 29 insertions(+)
diff --git a/qga/commands-posix.c b/qga/commands-posix.c
index 0ad73f3..6fc6003 100644
--- a/qga/commands-posix.c
+++
From: Jeff Cody jc...@redhat.com
During a commit of 'all' using the HMP non-live commit, the operation
is aborted and returns error on the first error enountered. When
non-COW drives are in use (e.g. ejected floppy, cdrom, or drives without
a backing parent), that means a commit all will return
Signed-off-by: Lei Li li...@linux.vnet.ibm.com
---
qga/commands-posix.c | 54
qga/qapi-schema.json | 27 ++
2 files changed, 81 insertions(+)
diff --git a/qga/commands-posix.c b/qga/commands-posix.c
index
Reuse common code in pcie_port, override the hardwired-to-0
bits per PCI Express spec.
No functional change but makes the code easier to follow.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Alex, I applied the following on top of your patch and
did a dump of the config space to verify
On Fri, Mar 01, 2013 at 09:13:38PM +0100, Kevin Wolf wrote:
diff --git a/block.c b/block.c
index bf93dd1..e0e3b99 100644
--- a/block.c
+++ b/block.c
@@ -665,15 +665,18 @@ static int bdrv_open_flags(BlockDriverState *bs, int
flags)
/*
* Common part for opening disk images and files
On Fri, Mar 01, 2013 at 09:13:34PM +0100, Kevin Wolf wrote:
Instead of constantly keeping complaining that we need this big -blockdev
things, let's start attacking individual parts of the project. Here is the
first part, allowing block drivers to provide additional -drive options.
Any
Il 28/02/2013 13:13, Hu Tao ha scritto:
This patch enables preservation of cpu runstate during save/load vm.
So when a vm is restored from snapshot, the cpu runstate is restored,
too.
I don't think this feature is worth breaking backwards migration
compatibility. It is usually handled at a
Il 28/02/2013 13:13, Hu Tao ha scritto:
From: Wen Congyang we...@cn.fujitsu.com
The guest should run after resetting it, but it does not run if its
old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
We don't set runstate to RUN_STATE_PAUSED when resetting the guest,
so the
Il 28/02/2013 13:13, Hu Tao ha scritto:
The guest will be in this state when it is panicked.
Signed-off-by: Wen Congyang we...@cn.fujitsu.com
Signed-off-by: Hu Tao hu...@cn.fujitsu.com
---
migration.c | 1 +
qapi-schema.json | 6 +-
qmp.c| 3 ++-
vl.c
Il 28/02/2013 13:13, Hu Tao ha scritto:
This event will be emited when the guest is panicked.
Signed-off-by: Wen Congyang we...@cn.fujitsu.com
---
include/monitor/monitor.h | 1 +
monitor.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/include/monitor/monitor.h
Il 28/02/2013 13:13, Hu Tao ha scritto:
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_EVENT_PORT when it is panciked. This patch introduces a new
qom device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's
On Sun, Mar 03, 2013 at 09:01:11AM +, Blue Swirl wrote:
On Sun, Mar 3, 2013 at 6:13 AM, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
This struct and functions provide some encapsulation of the uint32_t type to
make it more friendly for use as guest accessible device state. Bits
./qemu-upstream-latest -boot reboot-timeout=1000 ...
(after boot failed, VM waits for 1000 ms and try to reboot)
reboot-timeout parameter doesn't work now, I found this regression bug
was introduced by commit 59d6ca52a7eba5b1f4f2becf70fd446dccaf0a2e
Author: Kevin O'Connor ke...@koconnor.net
Il 28/02/2013 13:13, Hu Tao ha scritto:
Signed-off-by: Wen Congyang we...@cn.fujitsu.com
Signed-off-by: Hu Tao hu...@cn.fujitsu.com
---
hw/pc_piix.c| 9 -
qemu-options.hx | 3 ++-
vl.c| 4
3 files changed, 14 insertions(+), 2 deletions(-)
We cannot add
Il 03/03/2013 11:27, Alon Levy ha scritto:
Il 01/03/2013 13:45, Paolo Bonzini ha scritto:
Il 12/02/2013 14:05, Fabio Fantoni ha scritto:
I'm making patches to enable some qemu upstream features in xen
that are
missing in libxl.
I'm trying to do it just by giving arguments to qemu, and I want
On 03/01/2013 07:54 PM, Andreas Färber wrote:
Am 27.02.2013 18:25, schrieb Fabien Chouteau:
On 02/27/2013 05:58 PM, Peter Maydell wrote:
On 27 February 2013 16:37, Fabien Chouteau chout...@adacore.com wrote:
I'm making my first steps in the ARM world by looking at R4F
implementation. More
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
pc-bios/efi-e1000.rom| Bin 0 - 174080 bytes
pc-bios/efi-eepro100.rom | Bin 0 - 175104 bytes
pc-bios/efi-ne2k_pci.rom | Bin 0 - 173568 bytes
pc-bios/efi-pcnet.rom| Bin 0 - 173568 bytes
pc-bios/efi-rtl8139.rom | Bin 0 - 177152
Needed for efi support.
ipxe is grown a bit, so *not* recompiling the (non-efi) pxe roms
because that would make some pxe roms larger than 64k, which in
turn would be a guest-visible change because the rom bar size
grows from 64k to 128k.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
All PCI nics are switched to EFI-enabled roms by default. They are
composed from three images (legacy, efi ia32 efi x86), so classic
pxe booting will continue to work.
Exception: eepro100 is not switched, it uses a single rom for all
emulated eepro100 variants, then goes patch the rom header on
make -C roms pxerom will build the ipxe roms and update
the binaries in pc-bios/, i.e. it basically documents how
the build process of our current nic roms works.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
roms/Makefile | 21 +
1 file changed, 21 insertions(+)
diff
Hi,
This patch series adds efi support to our nic roms.
Patch #4 (carrying the binaries) is pretty big and
isn't sent to the list. If you wanna test without
compiling your own roms please pull the git tree
below.
cheers,
Gerd
The following changes since commit
make -C roms efirom will build rom binaries with EFI support.
They are composed from three images: legacy bios, efi ia32
and efi x64. So netbooting via SeaBIOS will continue to work
like it does today, and additionally we get network support
for EFI. This target needs the EfiRom utility (shipped
On 28/02/13 13:13, Hu Tao wrote:
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_EVENT_PORT when it is panciked. This patch introduces a new
qom device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's value.
Hi,
I am trying to run a PCI card as a pass-throughed device. The PCI driver
works well on physical PC but failed on a full-virtualized PC. The KVM
confiuration is OK as a pass-throughed network card works. I debuged the
PCI driver and found that the some registers of this PCI card should be
Il 03/03/2013 10:17, Gleb Natapov ha scritto:
On Thu, Feb 28, 2013 at 08:13:10PM +0800, Hu Tao wrote:
This series implements a new interface, kvm pv event, to notify host when
some events happen in guest. Right now there is one supported event: guest
panic.
What other event do you have in
On Mon, Jan 28, 2013 at 11:19:34AM +0800, Amos Kong wrote:
On Wed, Jan 23, 2013 at 06:41:44PM +0800, Amos Kong wrote:
On Tue, Jan 22, 2013 at 12:26:03PM -0600, Anthony Liguori wrote:
Eric Blake ebl...@redhat.com writes:
On 01/22/2013 08:52 AM, Amos Kong wrote:
Libvirt will need
On 03/01/2013 09:51 PM, Paul Brook wrote:
From GDB Remote Serial Protocol doc:
The bytes with the register are transmitted in target byte order.
/* Aliases for Q regs. */
nregs += 16;
if (reg nregs) {
-stfq_le_p(buf, env-vfp.regs[(reg - 32) * 2]);
Il 04/03/2013 11:10, Christian Borntraeger ha scritto:
+//disabled wait: we either
+//do a
+//monitor_protocol_event(QEVENT_GUEST_PANICKED, whatever);
+//or
+//or call into pvevent
r = EXCP_HALTED;
break;
On Mon, Mar 04, 2013 at 11:05:37AM +0100, Paolo Bonzini wrote:
Guest uses acpi_get_devices() to discover a platform device by
its name (QEMU0001). Then you put the driver for the platform device
into drivers/platform/x86/ and QEMU/kvm/Xen all will be able to use it.
Just to clarify it
Il 04/03/2013 11:21, Gleb Natapov ha scritto:
Just to clarify it for Hu Tao, the read from a random ioport is how the
ACPI code will detect presence of the device.
Actually no (at least in the long run, for the first version it may be
OK).
Agreed.
Since we want to move DSDT generation
On Fri, Mar 01, 2013 at 04:14:40PM -0700, Eric Blake wrote:
I understand the reason that fdsets exist (because NFS is stupid and
doesn't support labeling). But we aren't doing dynamic labeling of
/dev/random and I strongly suspect it's not on NFS anyway.
So why are we trying to pass
On 03/01/2013 09:58 PM, Paul Brook wrote:
+#ifdef TARGET_WORDS_BIGENDIAN
+if (arm_feature(env, ARM_FEATURE_V6)
+|| arm_feature(env, ARM_FEATURE_V7)) {
+/* IE and EE bits stay set for big-endian */
+env-cp15.c1_sys |= (1 31) | (1 25);
+}
+#endif
This is
On Fri, Mar 01, 2013 at 03:58:18PM -0300, Eduardo Habkost wrote:
On Fri, Mar 01, 2013 at 07:31:46PM +0100, Andreas Färber wrote:
Am 01.03.2013 14:12, schrieb Jiri Denemark:
On Thu, Feb 21, 2013 at 11:58:18 -0300, Eduardo Habkost wrote:
= Listing CPU models =
Requirement: libvirt
On Mon, Mar 04, 2013 at 11:28:05AM +0100, Paolo Bonzini wrote:
Il 04/03/2013 11:21, Gleb Natapov ha scritto:
Just to clarify it for Hu Tao, the read from a random ioport is how the
ACPI code will detect presence of the device.
Actually no (at least in the long run, for the first
Il 04/03/2013 11:43, Gleb Natapov ha scritto:
Anyhow, this does not apply to the next submission of this series. I
think we can agree to the compromise of using ACPI but still read the
port in _STA.
If you want to make ioport configurable I do not see how can we avoid
patching.
I want
On Fri, Mar 01, 2013 at 08:43:18AM +0100, Michal Privoznik wrote:
As of 5a49d3e9 we assume SPICE_PORT_EVENT_BREAK to be defined.
However, it is defined not in 0.12.2 what we require now, but in
0.12.3. Therefore in order to prevent build failure we must
adjust our minimal requirements.
---
This patch is fine but needs to be on qemu-devel@nongnu.org in addition
to qemu-trivial.
- Forwarded message from Stefan Berger stef...@linux.vnet.ibm.com -
Date: Fri, 01 Mar 2013 07:53:55 -0500
From: Stefan Berger stef...@linux.vnet.ibm.com
To: qemu-triv...@nongnu.org
Cc: Paolo Bonzini
On Fri, Mar 01, 2013 at 04:57:41PM +, Peter Maydell wrote:
The address_space field of PCIHostState was only ever written, never used.
Drop it completely.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
Noticed this when looking at converting versatile_pci to be a subclass
of
On Mon, Mar 04, 2013 at 11:49:07AM +0100, Paolo Bonzini wrote:
Il 04/03/2013 11:43, Gleb Natapov ha scritto:
Anyhow, this does not apply to the next submission of this series. I
think we can agree to the compromise of using ACPI but still read the
port in _STA.
If you want to make
Am 26.02.2013 18:40, schrieb Peter Maydell:
Implement support for using the KVM in-kernel GIC for ARM.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Andreas Färber afaer...@suse.de
Thanks,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF:
Ping!
Any further review on this? Id like to drop patch 8 (at it is
proof-of-concept only) and merge up to and including this. Andreas has
put RB to patches 1-6 already.
Regards,
Peter
On Mon, Feb 25, 2013 at 6:50 PM, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
Create a separate
On Sun, Mar 03, 2013 at 11:35:27AM +0200, Abel Gordon wrote:
Stefan Hajnoczi stefa...@gmail.com wrote on 01/03/2013 12:54:54 PM:
On Thu, Feb 28, 2013 at 08:20:08PM +0200, Abel Gordon wrote:
Stefan Hajnoczi stefa...@gmail.com wrote on 28/02/2013 04:43:04 PM:
I think extending and
Am 26.02.2013 18:40, schrieb Peter Maydell:
Convert the ARM GIC classes to use init/realize rather than
SysBusDevice::init. (We have to do them all in one patch to
avoid unconverted subclasses calling a nonexistent SysBusDevice
init function in the base class and crashing.)
Signed-off-by:
Il 04/03/2013 11:59, Gleb Natapov ha scritto:
I want to make the ioport configurable in the device, but the PIIX and
ICH9 (which are what the DSDT is written for) will always use port 0x505.
But the device is not part of PIIX or ICH9.
So is kvmclock, or kvmvapic. I think it makes sense to
Am 26.02.2013 18:40, schrieb Peter Maydell:
Drop the CPUARMState* argument from bank_number(), since we only
use it for passing to cpu_abort(). Use hw_error() instead.
This avoids propagating further interfaces using env pointers.
In the long term this function's callers need auditing to fix
On Mon, Mar 04, 2013 at 12:10:58PM +0100, Paolo Bonzini wrote:
Il 04/03/2013 11:59, Gleb Natapov ha scritto:
I want to make the ioport configurable in the device, but the PIIX and
ICH9 (which are what the DSDT is written for) will always use port 0x505.
But the device is not part of
Am 25.02.2013 18:08, schrieb Peter Maydell:
Make musicpal-misc into its own (trivial) qdev device, so we
can get rid of the abuse of sysbus_add_memory().
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
hw/musicpal.c | 28 +++-
1 file changed, 23
Am 02.03.2013 16:18, schrieb Sanjay Lal:
---
configure | 17 +++--
hw/mips/Makefile.objs | 2 +-
target-mips/Makefile.objs | 1 +
3 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
index bf5970f..5447661 100755
---
Il 04/03/2013 12:20, Gleb Natapov ha scritto:
On Mon, Mar 04, 2013 at 12:10:58PM +0100, Paolo Bonzini wrote:
It is additional device that
may or may not be present depending on a command line. So what if
someone configures debugcon or debugexit to use this port?
I haven't checked if
On 4 March 2013 19:10, Andreas Färber afaer...@suse.de wrote:
Am 26.02.2013 18:40, schrieb Peter Maydell:
if (s-num_cpu NCPU) {
-hw_error(requested %u CPUs exceeds GIC maximum %d\n,
- s-num_cpu, NCPU);
+error_setg(errp, requested %u CPUs exceeds GIC
On Mon, Mar 04, 2013 at 12:35:08PM +0100, Paolo Bonzini wrote:
Il 04/03/2013 12:20, Gleb Natapov ha scritto:
On Mon, Mar 04, 2013 at 12:10:58PM +0100, Paolo Bonzini wrote:
It is additional device that
may or may not be present depending on a command line. So what if
someone configures
On 4 March 2013 19:22, Andreas Färber afaer...@suse.de wrote:
Am 25.02.2013 18:08, schrieb Peter Maydell:
--- a/hw/musicpal.c
+++ b/hw/musicpal.c
@@ -1031,6 +1031,15 @@ static const TypeInfo mv88w8618_flashcfg_info = {
#define MP_BOARD_REVISION 0x31
+typedef struct {
+
Hello,
Am 02.03.2013 16:18, schrieb Sanjay Lal:
The following patchset implements KVM support for MIPS32 processors,
using Trap Emulate, with basic runtime binary translation to improve
performance.
[snip]
Please see http://wiki.qemu.org/Contribute/SubmitAPatch for some hints
on how to
Hi Peter,
Am 04.03.2013 10:01, schrieb Peter Crosthwaite:
Hi All. The clock controller module in the Zynq platform has the ability to
halt
and reset arbitrary devices, including the CPU. We use this feature to
implement
SMP Linux - the kernel halts CPU1 then rewrites the vector table to
Am 04.03.2013 12:50, schrieb Peter Maydell:
On 4 March 2013 19:10, Andreas Färber afaer...@suse.de wrote:
Am 26.02.2013 18:40, schrieb Peter Maydell:
if (s-num_cpu NCPU) {
-hw_error(requested %u CPUs exceeds GIC maximum %d\n,
- s-num_cpu, NCPU);
+
Hi
Please send in any agenda topics you are interested in.
Later, Juan.
Il 04/03/2013 12:52, Gleb Natapov ha scritto:
Same here, you can remove the panic event port and add debugcon at
0x505. That's the problematic case. But if the user goes to that
length, I think we can honestly say we don't care.
IMO there is a big difference between well know serial ISA
Here's version 8. This one includes Blue's typedef usage suggestion,
and gen_tb_start()/gen_tb_end() as required by Peter Maydell's recent
'get rid of cpu_tb_unlink()' patch series.
Please consider this version for inclusion in qemu.
Thanks!
AG
Anthony Green (4):
Add moxie target code
Add
Signed-off-by: Anthony Green gr...@moxielogic.com
---
disas.c | 6 +
disas/Makefile.objs | 1 +
disas/moxie.c | 360
include/disas/bfd.h | 2 +
4 files changed, 369 insertions(+)
create mode 100644 disas/moxie.c
diff
Signed-off-by: Anthony Green gr...@moxielogic.com
---
target-moxie/Makefile.objs |2 +
target-moxie/cpu.c | 172
target-moxie/cpu.h | 172
target-moxie/helper.c | 170
target-moxie/helper.h |9 +
target-moxie/machine.c | 27 ++
Signed-off-by: Anthony Green gr...@moxielogic.com
---
MAINTAINERS | 5 +
arch_init.c | 2 ++
configure | 9 -
cpu-exec.c| 2 ++
default-configs/moxie-softmmu.mak | 2 ++
qapi-schema.json
Signed-off-by: Anthony Green gr...@moxielogic.com
---
hw/moxie/Makefile.objs | 6 ++
hw/moxie/moxiesim.c| 174 +
include/sysemu/arch_init.h | 1 +
3 files changed, 181 insertions(+)
create mode 100644 hw/moxie/Makefile.objs
create
Hi Andreas,
On Mon, Mar 4, 2013 at 10:03 PM, Andreas Färber afaer...@suse.de wrote:
Hi Peter,
Am 04.03.2013 10:01, schrieb Peter Crosthwaite:
Hi All. The clock controller module in the Zynq platform has the ability to
halt
and reset arbitrary devices, including the CPU. We use this feature
On Thu, Feb 28, 2013 at 03:24:27PM +, Dietmar Maurer wrote:
Unfortunately, NBD add considerable overheads. I guess the socket
communications copies data.
This is really unnecessary if I can write directly to the output stream.
The disk is the bottleneck, not memory bandwidth.
Before posting another version of my patches [1], attempting to add
support for the new qcow format to libvirt, I would like to know if this
sounds reasonable:
A new format named 'qcow3' would be added, along with a features
sub-element for target.
volume
nameqcow3test/name
source
/source
On Fri, Mar 01, 2013 at 09:51:53AM +0800, Wenchao Xia wrote: 于 2013-2-28
0:22, Kevin Wolf 写道:
Am 27.02.2013 um 17:04 hat Markus Armbruster geschrieben:
Wenchao Xia xiaw...@linux.vnet.ibm.com writes:
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
Reviewed-by: Eric Blake
On Mon, Mar 04, 2013 at 01:58:12PM +0100, Ján Tomko wrote:
Before posting another version of my patches [1], attempting to add
support for the new qcow format to libvirt, I would like to know if this
sounds reasonable:
A new format named 'qcow3' would be added, along with a features
On Fri, Mar 01, 2013 at 09:47:29AM +0800, Wenchao Xia wrote:
于 2013-2-28 23:57, Stefan Hajnoczi 写道:
On Tue, Feb 26, 2013 at 06:40:14PM +0800, Wenchao Xia wrote:
This serial of patches does two things: merge some info code
in qemu-img, and add following interfaces:
1) qmp: query-images
2)
What are the details of the test?
Is it using 64 KB writes and have you tried 256 KB writes?
I use a modified 'qemu-img convert' at 64KB block size (I need 64KB for backup).
On 03/01/2013 09:58 PM, Paul Brook wrote:
+#ifdef TARGET_WORDS_BIGENDIAN
+if (arm_feature(env, ARM_FEATURE_V6)
+|| arm_feature(env, ARM_FEATURE_V7)) {
+/* IE and EE bits stay set for big-endian */
+env-cp15.c1_sys |= (1 31) | (1 25);
+}
+#endif
The bytes with the register are transmitted in target byte order.
/* Aliases for Q regs. */
nregs += 16;
if (reg nregs) {
-stfq_le_p(buf, env-vfp.regs[(reg - 32) * 2]);
-stfq_le_p(buf + 8, env-vfp.regs[(reg - 32) * 2 + 1]);
+
Gerd Hoffmann kra...@redhat.com writes:
Hi,
This patch series adds efi support to our nic roms.
Patch #4 (carrying the binaries) is pretty big and
isn't sent to the list. If you wanna test without
compiling your own roms please pull the git tree
below.
Looks pretty reasonable.
On Mon, Mar 04, 2013 at 05:45:02PM +0800, Amos Kong wrote:
./qemu-upstream-latest -boot reboot-timeout=1000 ...
(after boot failed, VM waits for 1000 ms and try to reboot)
[...]
romfile_add() is used to add rom files in the list.
When seabios calls boot_fail(), the list becomes empty,
Am 04.03.2013 um 14:16 hat Dietmar Maurer geschrieben:
What are the details of the test?
Is it using 64 KB writes and have you tried 256 KB writes?
I use a modified 'qemu-img convert' at 64KB block size (I need 64KB for
backup).
Maybe you'd better use a different output format that
Users have reported that qcow2 internal snapshot creation is slow. I filed a
bug report at https://bugs.launchpad.net/qemu/+bug/1126369.
This patch series reduces the time for qcow2 internal snapshot creation
significantly, from more than 3 minutes to under 1 second.
In the process of removing
update_refcount() affects the refcount cache, it does not write to disk.
Therefore bdrv_flush(bs-file) does nothing. We need to flush the
refcount cache in order to write out the refcount updates!
While we're here also add error returns when qcow2_cache_flush() fails.
Signed-off-by: Stefan
Am 04.03.2013 um 14:09 hat Daniel P. Berrange geschrieben:
On Mon, Mar 04, 2013 at 01:58:12PM +0100, Ján Tomko wrote:
Before posting another version of my patches [1], attempting to add
support for the new qcow format to libvirt, I would like to know if this
sounds reasonable:
A new
1 - 100 of 249 matches
Mail list logo
