This series reworks the SSI bus framework for SPI and add some new SPI
controllers and devices:
Patches 1-4 reworks SSI to add chip-select support to SPI devices and allow for
multiple SPI devices attached to the
same bus.
Patches 5-6 fix the SPI setup in the stellaris machine model.
Patch 7 i
From: Peter A. G. Crosthwaite
Removed assertion that only one device is attached to the SSI bus.
When multiple devices are attached, all slaves have their transfer function
called for transfers. Each device is responsible for knowing whether or not its
CS is active, and if not returning 0. The r
From: Peter A. G. Crosthwaite
Slave creation function that can be used to create an SSI slave without
qdev_init() being called. This give machine models a chance to set properties.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/ssi.c |9 +++--
hw/ssi.h |1 +
2 files changed, 8 inse
From: Peter A. G. Crosthwaite
stellaris_init() defines arrays of qemu_irq to decides what each of the GPIO
pins are connected to. This is ok for inputs (as an input can only have one
source) but is flawed for outputs as an output can connect to any number of
sinks. Removed the gpio_out array comp
From: Peter A. G. Crosthwaite
Removed the explicit SSI mux and wired the CS line directly up to the SSI
devices.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/ssd0323.c |1 +
hw/ssi-sd.c|1 +
hw/stellaris.c | 98 ++--
3 files
From: Peter A. G. Crosthwaite
Added device model for m25p80 style SPI flash family.
Signed-off-by: Peter A. G. Crosthwaite
---
changed from v7:
Debug print on select as well as deselect
Fixed data bit reversal
changed from v6:
Addressed Blue Swirl review
Constified TypeInfo
Added missing break
From: Peter A. G. Crosthwaite
Added maintainership for SSI, M25P80 and the Xilinx SPI controllers.
Signed-off-by: Peter A. G. Crosthwaite
---
MAINTAINERS |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 29aac4f..e25794b 100644
---
Added helper function to automatically connect SPI slaves based on the QOM child
nodes of a device. A SSI master device can call this routine to automatically
hook-up all child nodes to its SPI bus.
Signed-off-by: Peter Crosthwaite
---
hw/ssi.c | 33 +
From: Peter A. G. Crosthwaite
Added SPI controller to the reference design, with two n25q128 spi-flashes
connected.
Signed-off-by: Peter A. G. Crosthwaite
---
Changed since v7:
Increased number of spi flashes to 4
Fixed spi controller qdev name and property names (see prev patch)
Changed since
From: Peter A. G. Crosthwaite
Added a FIFO API that can be used to create and operate byte FIFOs.
Signed-off-by: Peter A. G. Crosthwaite
---
hw/Makefile.objs |1 +
hw/fifo.c| 78 ++
hw/fifo.h| 47 +
From: Peter A. G. Crosthwaite
Added default CS behaviour for SSI slaves. SSI devices can set a property
to enable CS behaviour which will create a GPIO on the device which is the
CS. Tristating of the bus on SSI transfers is implemented.
Signed-off-by: Peter A. G. Crosthwaite
---
Changed since
From: Peter A. G. Crosthwaite
Added the two SPI controllers to the zynq machine model. Attached two SPI flash
devices to each controller.
Signed-off-by: Peter A. G. Crosthwaite
---
changed from v7:
Increased number of spi flashes pre controller to 4
changed from v6:
removed (char*) cast to qdev
From: Peter A. G. Crosthwaite
Allow multiple qdev_init_gpio_in() calls for the one device. The first call will
define GPIOs 0-N-1, the next GPIOs N- ... . Allows different GPIOs to be handled
with different handlers. Needed when two levels of the QOM class heirachy both
define GPIO functionality,
From: Peter A. G. Crosthwaite
Added device model for the Xilinx Zynq SPI controller (SPIPS).
Signed-off-by: Peter A. G. Crosthwaite
---
Changed from v7:
Fixed &->&& logic on if condition is cs_select logic
Fixed MODE_SEL bit field definition
Changed from v6:
Addressed Blue Swirl review
s/interu
From: Peter A. G. Crosthwaite
Device model for xilinx XPS SPI controller (v2.0)
Signed-off-by: Peter A. G. Crosthwaite
---
changed from v7:
Fixed device name: s/xilinx,spi/xlnx.xps-spi
Fixed num-ss-bits property name: s/num-cs/num-ss-bits
changed from v4 (Near total rewrite):
removed timer dela
On 2012-10-01 18:20, Anthony Liguori wrote:
> Jan Kiszka writes:
>
>> If we built a target for a host that supports KVM in principle, set the
>> default accelerator to KVM as well. This also means the start of QEMU
>> will fail to start if KVM support turns out to be unavailable at
>> runtime.
>>
On 2012-10-03 08:58, Michael Tokarev wrote:
> On 02.10.2012 11:46, Markus Armbruster wrote:
>> "Daniel P. Berrange" writes:
>
>>> IMHO, default to KVM, fallback to TCG is the most friendly default
>>> behaviour.
>>
>> Friendly perhaps, generating an infinite series of questions "why is my
>> gues
It was missing for leon3 and mips_fulong2e.
Signed-off-by: Stefan Weil
---
hw/leon3.c |2 +-
hw/mips/mips_fulong2e.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/leon3.c b/hw/leon3.c
index 878d3aa..7a9729d 100644
--- a/hw/leon3.c
+++ b/hw/leon3.c
Resending it again as I got no comments and seems to have been ignored so
far. These patches simplify the vmware_vga by removing duplicated info
from its local state and make it work with more guest drivers (in
particular with the very simple OpenStep VMWareFB driver) that do not use
the fifo w
Removed info from vmsvga_state that is available from elsewhere and
thus was duplicated here unnecessarily. Also includes some coding
style fixes suggested by checkpatch.pl.
Signed-off-by: BALATON Zoltan
---
console.h | 20 ++
hw/vmware_vga.c | 196 +++--
According to the documentation drivers using this device should read
FB_SIZE before enabling the device to know what memory to map. This
would not work if we return 0 before enabled.
Signed-off-by: BALATON Zoltan
---
hw/vmware_vga.c | 13 -
1 file changed, 8 insertions(+), 5 delet
Postpone stopping the dirty log to the point where the command fifo is
configured to allow drivers which don't use the fifo to work too.
(Without this the picture rendered into the vram never got to the
screen and the DIRECT_VRAM option meant to support this case was
removed a year ago.)
Signed-o
Il 03/10/2012 11:30, BALATON Zoltan ha scritto:
> Removed info from vmsvga_state that is available from elsewhere and
> thus was duplicated here unnecessarily. Also includes some coding
> style fixes suggested by checkpatch.pl.
Coding style fixes ideally would be in a separate patch.
A couple nit
Il 03/10/2012 11:30, BALATON Zoltan ha scritto:
> According to the documentation drivers using this device should read
> FB_SIZE before enabling the device to know what memory to map. This
> would not work if we return 0 before enabled.
>
> Signed-off-by: BALATON Zoltan
> ---
> hw/vmware_vga.c |
Il 03/10/2012 11:31, BALATON Zoltan ha scritto:
> Postpone stopping the dirty log to the point where the command fifo is
> configured to allow drivers which don't use the fifo to work too.
> (Without this the picture rendered into the vram never got to the
> screen and the DIRECT_VRAM option meant
Il 02/10/2012 22:12, Alex Williamson ha scritto:
> On Tue, 2012-10-02 at 14:55 -0500, Anthony Liguori wrote:
>> Alex Williamson writes:
>>
>>> In the event that a pci-assign device is added to a chipset that
>>> hasn't yet implemented the INTx routing interface, exit gracefully
>>> instead of kill
On Mon, Oct 01, 2012 at 03:26:05PM +0200, Jan Kiszka wrote:
> On 2012-10-01 15:19, Anthony Liguori wrote:
> > Jan Kiszka writes:
> >
> >> On 2012-10-01 11:31, Marcelo Tosatti wrote:
> >>
> >> It's not just about default configs. We need to validate if the
> >> migration formats are truly compatib
On 2012-10-03 11:55, Gleb Natapov wrote:
> On Mon, Oct 01, 2012 at 03:26:05PM +0200, Jan Kiszka wrote:
>> On 2012-10-01 15:19, Anthony Liguori wrote:
>>> Jan Kiszka writes:
>>>
On 2012-10-01 11:31, Marcelo Tosatti wrote:
It's not just about default configs. We need to validate if th
On Wed, Oct 03, 2012 at 12:06:57PM +0200, Jan Kiszka wrote:
> On 2012-10-03 11:55, Gleb Natapov wrote:
> > On Mon, Oct 01, 2012 at 03:26:05PM +0200, Jan Kiszka wrote:
> >> On 2012-10-01 15:19, Anthony Liguori wrote:
> >>> Jan Kiszka writes:
> >>>
> On 2012-10-01 11:31, Marcelo Tosatti wrote:
Il 17/09/2012 18:43, Paolo Bonzini ha scritto:
> This patch doesn't seem much useful alone, I must admit. However,
> it makes sense as part of the upcoming directory reorganization,
> where I want to have include/net/tap.h as the net<->hw interface
> for tap. Then having both net/tap.h and includ
Commit 80019541e9c13fab476bee35edcef3e11646222c from qemu-kvm.git.
From: Jan Kiszka
Use global properties to emulate -no-kvm-pit-reinjection
Signed-off-by: Marcelo Tosatti
Index: qemu-compat-kvm/vl.c
===
--- qemu-compat-kvm.orig/
Commit d527b774878defc27f317cdde19b5c54fd0d5666 from qemu-kvm.git.
From: Jan Kiszka
Add a warning that there is no effect anymore.
Signed-off-by: Marcelo Tosatti
Index: qemu-compat-kvm/vl.c
===
--- qemu-compat-kvm.orig/vl.c
+++ q
Commit 841280b6c224ea2c6edc2f5afc2add513c85181d from qemu-kvm.git.
From: Jan Kiszka
We do not want to maintain this option forever. It will be removed after
a grace period of a few releases. So warn the user that this option has
no effect and will become invalid soon.
Signed-off-by: Marcelo Tos
As discussed on yesterdays qemu call, follows qemu-kvm compat patches
for qemu:
- command line compatibility
- allow configurable ram size for cirrus
Allow RAM size to be configurable for cirrus, to allow migration
compatibility from qemu-kvm.
Signed-off-by: Marcelo Tosatti
Index: qemu-compat-kvm/hw/cirrus_vga.c
===
--- qemu-compat-kvm.orig/hw/cirrus_vga.c
+++ qemu-compat-kvm/hw
Commit e81dda195556e72f8cd294998296c1051aab30a8 from qemu-kvm.git.
From: Jan Kiszka
Leave the related command line option in place, just
issuing a warning that it has no function anymore.
Signed-off-by: Marcelo Tosatti
Index: qemu-compat-kvm/vl.c
==
On 10/03/2012 06:55 AM, Gleb Natapov wrote:
On Mon, Oct 01, 2012 at 03:26:05PM +0200, Jan Kiszka wrote:
On 2012-10-01 15:19, Anthony Liguori wrote:
Jan Kiszka writes:
On 2012-10-01 11:31, Marcelo Tosatti wrote:
It's not just about default configs. We need to validate if the
migration format
Commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d from qemu-kvm.git.
From: Jan Kiszka
Upstream is moving towards this mechanism, so start using it in qemu-kvm
already to configure the specific defaults: kvm enabled on, just like
in-kernel irqchips.
Signed-off-by: Marcelo Tosatti
Index: qemu
From: Bharat Bhushan
The CCSR memory region is exported to pci device. The MSI interrupt
generation is the main reason to export the CCSR region to PCI device.
This put the requirement to move mpic under CCSR region, but logically
all devices should be under CCSR.
So First patch creates the CCSR
All devices are also placed under CCSR memory region.
The CCSR memory region is exported to pci device. The MSI interrupt
generation is the main reason to export the CCSR region to PCI device.
This put the requirement to move mpic under CCSR region, but logically
all devices should be under CCSR. S
PCI Root complex have TYPE-1 configuration header while PCI endpoint
have type-0 configuration header. The type-1 configuration header have
a BAR (BAR0). In Freescale PCI controller BAR0 is used for mapping pci
address space to CCSR address space. This can used for 2 purposes: 1)
for MSI interrupt
On 03.10.2012, at 13:49, Bharat Bhushan wrote:
> All devices are also placed under CCSR memory region.
> The CCSR memory region is exported to pci device. The MSI interrupt
> generation is the main reason to export the CCSR region to PCI device.
> This put the requirement to move mpic under CCSR
On 03.10.2012, at 13:50, Bharat Bhushan wrote:
> PCI Root complex have TYPE-1 configuration header while PCI endpoint
> have type-0 configuration header. The type-1 configuration header have
> a BAR (BAR0). In Freescale PCI controller BAR0 is used for mapping pci
> address space to CCSR address s
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Wednesday, October 03, 2012 5:39 PM
> To: Bhushan Bharat-R65777
> Cc: qemu-devel@nongnu.org; qemu-...@nongnu.org; Bhushan Bharat-R65777
> Subject: Re: [PATCH 1/2] e500: Adding CCSR memory region
>
>
> On 03.10.20
>> +const uint64_t *qb_get_virt_size(const QBlockStaticInfo *info)
>> +{
>> +return info->member_addr->virt_size;
>
>Please change this to:
>
> QBlockStaticInfoAddr addrs;
> qb_setup_info_addr(info, &addrs);
> return *addrs->virt_size;
>
>and similarly for the others.
>
>QBlockStati
On 03.10.2012, at 14:16, Bhushan Bharat-R65777 wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Wednesday, October 03, 2012 5:39 PM
>> To: Bhushan Bharat-R65777
>> Cc: qemu-devel@nongnu.org; qemu-...@nongnu.org; Bhushan Bharat-R65777
>> Subject: R
Il 03/10/2012 13:31, wenchao xia ha scritto:
>>> +const uint64_t *qb_get_virt_size(const QBlockStaticInfo *info)
>>> +{
>>> +return info->member_addr->virt_size;
>>
>> Please change this to:
>>
>> QBlockStaticInfoAddr addrs;
>> qb_setup_info_addr(info, &addrs);
>> return *addrs->vir
Paolo Bonzini writes:
> Il 02/10/2012 22:12, Alex Williamson ha scritto:
>> On Tue, 2012-10-02 at 14:55 -0500, Anthony Liguori wrote:
>>> Alex Williamson writes:
>>>
In the event that a pci-assign device is added to a chipset that
hasn't yet implemented the INTx routing interface, exit
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Wednesday, October 03, 2012 5:41 PM
> To: Bhushan Bharat-R65777
> Cc: qemu-devel qemu-devel; qemu-...@nongnu.org List; Bhushan Bharat-R65777;
> Avi
> Kivity
> Subject: Re: [PATCH 2/2] Adding BAR0 for e500 PCI cont
On 3 October 2012 14:09, Peter Crosthwaite
wrote:
> Ping!
>
> Should this go via arm-devs or create a zynq-specific queue?
I'm happy to put it in arm-devs if that's easier.
-- PMM
Il 03/10/2012 12:57, Lucas Meneghel Rodrigues ha scritto:
> Yep, I did send patches with the testdev device present on qemu-kvm.git
> to qemu.git a while ago, but there were many comments on the review, I
> ended up not implementing everything that was asked and the patches were
> archived.
>
> If
On Wed, Oct 03, 2012 at 03:19:56PM +0200, Paolo Bonzini wrote:
> Il 03/10/2012 12:57, Lucas Meneghel Rodrigues ha scritto:
> > Yep, I did send patches with the testdev device present on qemu-kvm.git
> > to qemu.git a while ago, but there were many comments on the review, I
> > ended up not implemen
The problem here is:
- The CPU object can't define its APIC ID itself, it has to be
defined by the creator of the CPU object
- The object instance_init() function can't get extra arguments
- I don't want to add a APIC ID argument to x86_cpu_realize(), as it
should eventually become a Obje
Ping!
Should this go via arm-devs or create a zynq-specific queue?
Regards,
Peter
On Thu, Sep 27, 2012 at 11:18 AM, Peter Crosthwaite
wrote:
> From: Soren Brinkmann
>
> A missing call to qemu_set_irq() when reading the IRQ register
> required SW to write to the IRQ register to acknowledge an
>
We can make it a child of a generic "machine" class later, but right now
a "PC" class is needed to allow global-properties to control some
details of CPU creation on the PC code.
Signed-off-by: Eduardo Habkost
---
hw/pc.c | 18 ++
hw/pc.h | 6 ++
2 files changed, 24 insertio
This changes FW_CFG_MAX_CPUS and FW_CFG_NUMA to use apic_id_for_cpu(),
so the NUMA table can be based on the APIC IDs, instead of CPU index
(SeaBIOS knows nothing about CPU indexes, just APIC IDs).
Changes v1 -> v2:
- Get PC object as argument
- Add more detailed comments explaining the reason f
This will allow each architecture to define how the VCPU ID is set on
the KVM_CREATE_VCPU ioctl call.
Signed-off-by: Eduardo Habkost
---
kvm-all.c | 2 +-
kvm.h | 3 +++
target-i386/kvm.c | 5 +
target-ppc/kvm.c | 5 +
target-s390x/kvm.c | 5 +
5 files change
Needed for the definition of fprint_function.
This is not necessary right now, but it will be necessary if code that
doesn't include cpu-common.h includes cpus.h.
Signed-off-by: Eduardo Habkost
---
cpus.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/cpus.h b/cpus.h
index 81bd817..b7c37
This keeps compatibility on machine-types pc-1.2 and older, and prints a
warning in case the requested configuration won't get the correct
topology.
At first I was going to use object_property_add() on PC instance_init
function, but this wouldn't allow us to use global properties to set
it[1]. So
The current behavior (setting APIC ID = CPU index) is kept, but this
will allow the PC code to set the proper CPU topology, later.
Signed-off-by: Eduardo Habkost
---
hw/pc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index a8788de..c64c218 10064
The CPU ID in KVM is supposed to be the APIC ID, so change the
KVM_CREATE_VCPU call to match it. The current behavior didn't break
anything yet because today the APIC ID is assumed to be == the CPU
index, but this won't be true in the future.
Chagnes v1 -> v2:
- Change only i386 code (kvm_arch_vc
Currently we need a way to calculate the Initial APIC ID using only the
CPU index (without needing a CPU object), as the NUMA fw_cfg data is
APIC-ID-based, and may include data for hotplug CPUs (that don't exist
yet), up to max_cpus.
Changes v2 -> v3:
- Move the whole code to hw/pc.c, now only t
Am 03.10.2012 11:19, schrieb Stefan Weil:
> It was missing for leon3 and mips_fulong2e.
>
> Signed-off-by: Stefan Weil
Reviewed-by: Andreas Färber
/-F
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
This allows callers of cpu_x86_init() to override the APIC ID, in case
it needs to build a specific cores/threads topology.
Because *-user doesn't have any concept of CPU topology, we do not
require every caller to specify an APIC ID. So a negative value will
indicate that the CPU index can be use
Add an extra argument to:
- pc_memory_init()
- bochs_bios_init()
- pc_cpus_init()
- pc_new_cpu()
Signed-off-by: Eduardo Habkost
---
hw/pc.c | 13 +++--
hw/pc.h | 5 +++--
hw/pc_piix.c | 4 ++--
3 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/hw/pc.c b/hw/
It would be interesting to make the generic machine intialization code
create a machine object instead, but changing the machine initialization
function signature is a nightmare, so by now I am creating the object
inside pc_init1().
The object is not used for anything by now, but it will be used d
Changes v2 -> v3:
- Add documentation pointers to the code
- Rename bits_for_count() to bitwidth_for_count()
- Remove unused apicid_*_id() functions
Changes v1 -> v2:
- Support 32-bit APIC IDs (in case x2APIC is going to be used)
- Coding style changes
- Use TARGET_I386_TOPOLOGY_H instead of
Bug description:
The CPU APIC IDs generated by QEMU are broken if the number of cores-per-socket
or threads-per-core are not powers of 2, as the bits on the APIC ID do not
correspond to what's expected to reflect the CPU sockets/cores/threads
topology[1].
[1]
http://software.intel.com/en-us/arti
It's not up to the CPU object to decide its APIC ID, but to the CPU
object creator (that knows about the CPU sockets, cores, and threads
topology).
This keeps the current APIC ID == CPU index behavior, by now.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c| 4 ++--
target-i386/cpu.h
On Sun, Sep 30, 2012 at 09:50:07PM -0400, Amos Kong wrote:
> - Original Message -
> > On Thu, Sep 20, 2012 at 09:46:41AM -0300, Marcelo Tosatti wrote:
> > > On Thu, Sep 20, 2012 at 01:55:20PM +0530, Amit Shah wrote:
> > > > Commit f349c12c0434e29c79ecde89029320c4002f7253 added the guest
> >
Hi Anthony,
please pull from the following tree based on
e744c06fca438dc08271e626034e632a270c91c8:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git xen-2012-10-03
Anthony PERARD (6):
xen: Fix, no unplug of pt device by platform device.
QMP, Introduce xen-set-global-dirty-log comm
use cpu_physical_memory_is_io() instead.
Signed-off-by: Avi Kivity
---
target-s390x/misc_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-s390x/misc_helper.c b/target-s390x/misc_helper.c
index e9b3cae..2da4c90 100644
--- a/target-s390x/misc_helper.c
+++ b/targe
To make unit tests that depend on target-specific files, use
check-unit--y and test-obj--y.
Signed-off-by: Eduardo Habkost
---
tests/Makefile | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/tests/Makefile b/tests/Makefile
index 26a67ce..ce4f6f2 100644
--- a/
PC will not use max_cpus for that field, so move it outside the common
code so it can use a different value on PC.
Signed-off-by: Eduardo Habkost
---
hw/fw_cfg.c | 1 -
hw/pc.c | 2 +-
hw/ppc_newworld.c | 1 +
hw/ppc_oldworld.c | 1 +
hw/sun4m.c| 3 +++
hw/sun4u.c
Changes v1 -> v2:
- Coding style change: break too-long line
Signed-off-by: Eduardo Habkost
---
hw/apic.c | 35 ++-
1 file changed, 18 insertions(+), 17 deletions(-)
diff --git a/hw/apic.c b/hw/apic.c
index 38e..e1f633a 100644
--- a/hw/apic.c
+++ b/hw/apic.c
This will help reduce the qemu-common.h dependency hell.
Signed-off-by: Eduardo Habkost
---
qemu-common.h | 57 ++
qemu-stdio.h | 73 +++
2 files changed, 75 insertions(+), 55 deletions(-)
creat
I cannot tell anything about upsteam, I'm going to try it
out now, but in general I tend to stay as close to
distro/yum version as possible,
so for 6.3 rhel it is tedious way of grabbing and compiling
everything that is needed
where it seems RHEL stands it the reservation that VGA
pass-though i
These functions help maintaining homogeneous formatting of error
messages that include strerror values.
Signed-off-by: Paolo Bonzini
---
error.c | 28
error.h | 9 +
2 file modificati, 37 inserzioni(+)
diff --git a/error.c b/error.c
index 1f05fc4..128d88c 1
Signed-off-by: Paolo Bonzini
---
migration-tcp.c | 8 +---
migration.c | 13 +++--
2 file modificati, 12 inserzioni(+), 9 rimozioni(-)
diff --git a/migration-tcp.c b/migration-tcp.c
index a15c2b8..78337a3 100644
--- a/migration-tcp.c
+++ b/migration-tcp.c
@@ -71,14 +71,16 @@ sta
perror and fprintf can be removed because all clients can now consume
Errors properly. However, we need to change the non-blocking connect
handlers to take an Error, in order to improve error handling for
migration with the TCP protocol.
Signed-off-by: Paolo Bonzini
---
qemu-sockets.c | 15
Before:
$ qemu-system-x86_64 -monitor tcp:localhost:6000
(starts despite error)
$ qemu-system-x86_64 -monitor tcp:foo.bar:12345
getaddrinfo(foo.bar,12345): Name or service not known
chardev: opening backend "socket" failed
$ qemu-system-x86_64 -monitor tcp:localhost:443,s
Reviewed-by: Luiz Capitulino
Signed-off-by: Paolo Bonzini
---
qemu-sockets.c | 41 +
1 file modificato, 21 inserzioni(+), 20 rimozioni(-)
diff --git a/qemu-sockets.c b/qemu-sockets.c
index 6f13121..55669e9 100644
--- a/qemu-sockets.c
+++ b/qemu-sockets.c
Marcelo Tosatti writes:
> Commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d from qemu-kvm.git.
>
> From: Jan Kiszka
>
> Upstream is moving towards this mechanism, so start using it in qemu-kvm
> already to configure the specific defaults: kvm enabled on, just like
> in-kernel irqchips.
>
> Si
Marcelo Tosatti writes:
> Commit e81dda195556e72f8cd294998296c1051aab30a8 from qemu-kvm.git.
>
> From: Jan Kiszka
>
> Leave the related command line option in place, just
> issuing a warning that it has no function anymore.
>
> Signed-off-by: Marcelo Tosatti
Reviewed-by: Anthony Liguori
Rega
Marcelo Tosatti writes:
> Commit 80019541e9c13fab476bee35edcef3e11646222c from qemu-kvm.git.
>
> From: Jan Kiszka
>
> Use global properties to emulate -no-kvm-pit-reinjection
>
> Signed-off-by: Marcelo Tosatti
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
>
> Index: qemu-compat-kvm
Marcelo Tosatti writes:
> Commit 841280b6c224ea2c6edc2f5afc2add513c85181d from qemu-kvm.git.
>
> From: Jan Kiszka
>
> We do not want to maintain this option forever. It will be removed after
> a grace period of a few releases. So warn the user that this option has
> no effect and will become inv
Marcelo Tosatti writes:
> Commit d527b774878defc27f317cdde19b5c54fd0d5666 from qemu-kvm.git.
>
> From: Jan Kiszka
>
> Add a warning that there is no effect anymore.
>
> Signed-off-by: Marcelo Tosatti
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
>
> Index: qemu-compat-kvm/vl.c
> ==
Marcelo Tosatti writes:
> As discussed on yesterdays qemu call, follows qemu-kvm compat patches
> for qemu:
>
> - command line compatibility
> - allow configurable ram size for cirrus
Whole thing looks good. I'll apply it directly to get it into qemu.git
faster.
Thanks.
Regards,
An
On Wed, 2012-10-03 at 15:30 +0100, lejeczek wrote:
> I cannot tell anything about upsteam, I'm going to try it
> out now, but in general I tend to stay as close to
> distro/yum version as possible,
> so for 6.3 rhel it is tedious way of grabbing and compiling
> everything that is needed
> where
On Wed, Oct 03, 2012 at 04:38:10PM +0200, Paolo Bonzini wrote:
> Il 03/10/2012 15:28, Eduardo Habkost ha scritto:
> > We can make it a child of a generic "machine" class later, but right now
> > a "PC" class is needed to allow global-properties to control some
> > details of CPU creation on the PC
Il 03/10/2012 15:28, Eduardo Habkost ha scritto:
> It would be interesting to make the generic machine intialization code
> create a machine object instead, but changing the machine initialization
> function signature is a nightmare, so by now I am creating the object
> inside pc_init1().
>
> The
Marcelo Tosatti writes:
> Allow RAM size to be configurable for cirrus, to allow migration
> compatibility from qemu-kvm.
>
> Signed-off-by: Marcelo Tosatti
Reviewed-by: Anthony Liguori
Regards,
Anthony Liguori
>
> Index: qemu-compat-kvm/hw/cirrus_vga.c
> ==
Il 03/10/2012 16:48, Eduardo Habkost ha scritto:
>> >
>> > Does it need to be a Device, or can it be a normal Object (or for
>> > clarity a derivative of TYPE_CONTAINER)?
> It needs to be a Device because that's the only way to use global
> properties, today.
>
> I have some experimental patches
On Wed, Oct 03, 2012 at 04:40:06PM +0200, Paolo Bonzini wrote:
> Il 03/10/2012 15:28, Eduardo Habkost ha scritto:
> > It would be interesting to make the generic machine intialization code
> > create a machine object instead, but changing the machine initialization
> > function signature is a night
Il 03/10/2012 16:53, Eduardo Habkost ha scritto:
>> >
>> > Can you add a hook to QEMUMachine so that this object is created by
>> > qdev_get_machine() and ends up at /machine?
> Oh, I didn't know there was an existing "machine" object already, I
> didn't know qdev_get_machine().
>
> Shouldn't /ma
Before:
$ qemu-system-x86_64 -monitor udp:localhost:631@localhost:631
inet_dgram_opts: bind(ipv4,127.0.0.1,631): OK
inet_dgram_opts failed
chardev: opening backend "udp" failed
After:
$ x86_64-softmmu/qemu-system-x86_64 -monitor udp:localhost:631@localhost:631
qemu-system
Signed-off-by: Paolo Bonzini
---
qga/channel-posix.c | 8 +---
1 file modificato, 5 inserzioni(+), 3 rimozioni(-)
diff --git a/qga/channel-posix.c b/qga/channel-posix.c
index e22eee6..d152827 100644
--- a/qga/channel-posix.c
+++ b/qga/channel-posix.c
@@ -181,9 +181,11 @@ static gboolean ga_c
Signed-off-by: Paolo Bonzini
---
qemu-char.c| 2 +-
qemu-sockets.c | 78 +-
qemu_socket.h | 6 -
3 file modificati, 72 inserzioni(+), 14 rimozioni(-)
diff --git a/qemu-char.c b/qemu-char.c
index 3cc6cb5..8ebd582 100644
--- a/qemu
On Tue, Oct 02, 2012 at 05:38:45PM -0300, Eduardo Habkost wrote:
> (Now replying on the right thread, to keep the discussion in the right
> place. I don't know how I ended up replying to a pre-historic version of
> the patch, sorry.)
>
> On Tue, Oct 02, 2012 at 05:36:59PM +0200, Igor Mammedov wrot
On Wed, Oct 03, 2012 at 09:40:17AM -0500, Anthony Liguori wrote:
> Marcelo Tosatti writes:
>
> > Commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d from qemu-kvm.git.
> >
> > From: Jan Kiszka
> >
> > Upstream is moving towards this mechanism, so start using it in qemu-kvm
> > already to config
1 - 100 of 218 matches
Mail list logo
