Il 22/06/2014 10:25, Chen, Tiejun ha scritto:
In qemu-upstream, as you commented we can't create this as a ISA class
type explicitly.
Note I didn't say that QEMU doesn't like having two ISA bridges.
I commented that the firmware will see two ISA bridges and will try to
initialize both of them
On Wed, 2014-06-25 at 08:20 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 24, 2014 at 03:02:03PM -0300, Eduardo Habkost wrote:
> > The QEMU_COMPAT_* macros will contain compat properties that are not
> > specific to PC, and may be reused by other machine-types.
> >
> > PC-specific properties were
On Wed, Jun 25, 2014 at 10:17:18AM +0800, Tiejun Chen wrote:
> ISA bridge is needed since Intel gfx drive will probe with Dev31:Fun0
> to make graphics device passthrough work well for VMM, that only need
> to expose this pseudo ISA bridge to let driver know the real hardware
> underneath.
>
> The
Hi!
VMStateDescription supports enclosed VMStateDescription's via .vmsd. This
is used in multiple places and VMStateDescription definitions look the same
way - name, version_id, minimum_version_id, etc.
QEMU handles first level VMStateDescription and enclosed VMStateDescription
slightly different
On Wed, Jun 25, 2014 at 10:17:17AM +0800, Tiejun Chen wrote:
> basic gfx passthrough support:
> - add a vga type for gfx passthrough
> - retrieve VGA bios from sysfs, then load it to guest at 0xC
> - register/unregister legacy VGA I/O ports and MMIOs for passthrough GFX
>
> The original patch
Il 25/06/2014 04:17, Tiejun Chen ha scritto:
+int pci_create_pch(PCIBus *bus)
+{
+XenHostPCIDevice hdev;
+int r = 0;
+
+if (!xen_has_gfx_passthru) {
+return r;
+}
+
You could make this an assertion, since the function is never called
with xen_has_gfx_passthru == 0. Or
Il 25/06/2014 04:17, Tiejun Chen ha scritto:
+if (xen_enabled() && xen_has_gfx_passthru) {
+d = pci_create_simple(b, 0, TYPE_I440FX_XEN_PCI_DEVICE);
+*pi440fx_state = I440FX_XEN_PCI_DEVICE(d);
+pci_create_pch(b);
+} else {
+d = pci_create_simple(b, 0, TYPE_
Il 25/06/2014 04:17, Tiejun Chen ha scritto:
+static int create_pseudo_pch_isa_bridge(PCIBus *bus, XenHostPCIDevice *hdev)
+{
+struct PCIDevice *dev;
+
+char rid;
+
+/* We havt to use a simple PCI device to fake this ISA bridge
+ * to avoid making some confusion to BIOS and ACPI.
Il 25/06/2014 04:17, Tiejun Chen ha scritto:
+static int get_vgabios(unsigned char *buf, XenHostPCIDevice *dev)
+{
+char rom_file[64];
+FILE *fp;
+uint8_t val;
+struct stat st;
+uint16_t magic = 0;
+int ret = 0;
+
+snprintf(rom_file, sizeof(rom_file),
+ "/s
On Tue, 24 Jun 2014 22:20:50 +0300
Marcel Apfelbaum wrote:
> On Tue, 2014-06-24 at 15:02 -0300, Eduardo Habkost wrote:
> > The QEMU_COMPAT_* macros will contain compat properties that are not
> > specific to PC, and may be reused by other machine-types.
> >
> > PC-specific properties were left o
Il 25/06/2014 04:17, Tiejun Chen ha scritto:
* Don't set that ISA class property, instead, just fake this ISA bridge
with 00:1f.0.
How are you going to make this work for Q35 or another PCIe machine that
already has an ISA bridge at 00:1f.0?
Paolo
Il 25/06/2014 02:08, Xiongzi Ge ha scritto:
Will the cache data in the guest be migrated to the other host?
Again, cache data is _not_ managed by QEMU. It is managed by the guest
kernel. Its content and state is migrated together with the rest of RAM.
Paolo
On Sat, Jun 14, 2014 at 09:38:30PM +0200, Max Reitz wrote:
> On 12.06.2014 05:54, Hu Tao wrote:
> >This patch adds a new option preallocation for raw format, and implements
> >full preallocation.
> >
> >Signed-off-by: Hu Tao
> >---
> > block/raw-posix.c | 59
> > +
Am 18.06.2014 08:43, schrieb Paolo Bonzini:
> This will let threads other than the I/O thread raise QMP events.
>
> GIOChannel is thread-safe, and send and receive state is usually
> well-separated. The only driver that requires some care is the
> pty driver, where some of the state is shared by
On Tue, Jun 24, 2014 at 07:57:55PM -0300, Eduardo Habkost wrote:
> The property name is "prog_if", not "prof_if".
>
> Signed-off-by: Eduardo Habkost
> Cc: BALATON Zoltan
Should be reported-by, by the way.
Cc: means "I have notified this person just in case".
> ---
> include/hw/i386/pc.h | 2 +
On Wed, Jun 25, 2014 at 09:00:59AM +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 24, 2014 at 07:57:55PM -0300, Eduardo Habkost wrote:
> > The property name is "prog_if", not "prof_if".
> >
> > Signed-off-by: Eduardo Habkost
> > Cc: BALATON Zoltan
>
> Should be reported-by, by the way.
> Cc: me
On Tue, Jun 24, 2014 at 07:57:55PM -0300, Eduardo Habkost wrote:
> The property name is "prog_if", not "prof_if".
>
> Signed-off-by: Eduardo Habkost
> Cc: BALATON Zoltan
Applied, thanks!
> ---
> include/hw/i386/pc.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/inc
On Tue, Jun 24, 2014 at 11:04:43PM -0300, Eduardo Habkost wrote:
> This series is an attempt to make the compat_props lists from the PC code
> reusable by other machine-types. All the compat bits that are on those lists
> are
> not tied to a specific machine-type, but instead to the device code th
On Tue, Jun 24, 2014 at 11:04:45PM -0300, Eduardo Habkost wrote:
> The QEMU_COMPAT_* macros will contain compat properties that are not
> specific to PC, and may be reused by other machine-types.
>
> The compat properties for PC-specific devices were moved to
> QEMU_COMPAT_* too, because they are
On Tue, Jun 24, 2014 at 11:04:44PM -0300, Eduardo Habkost wrote:
> For each compat property on PC_Q35_COMPAT_*, there are only two
> possibilities:
>
> * If the device is never instantiated when using a machine other than
>pc-q35, then the compat property can be safely added to
>PC_COMPAT
On Sat, Jun 14, 2014 at 09:17:02PM +0200, Max Reitz wrote:
> On 12.06.2014 05:54, Hu Tao wrote:
> >This patch prepares for the subsequent patches.
> >
> >Reviewed-by: Fam Zheng
> >Reviewed-by: Eric Blake
> >Signed-off-by: Hu Tao
> >---
> > block/qcow2.c| 8
> > qapi-schema.json |
On Fri, Jun 20, 2014 at 08:37:51PM +0200, Max Reitz wrote:
> On 20.06.2014 10:25, Hu Tao wrote:
> >On Sat, Jun 14, 2014 at 10:37:33PM +0200, Max Reitz wrote:
> >>On 12.06.2014 05:54, Hu Tao wrote:
> >>>This adds a preallocation=full mode to qcow2 image creation, which
> >>>creates a non-sparse imag
On Wed, Jun 25, 2014 at 12:39:39PM +1000, Alexey Kardashevskiy wrote:
> On 06/25/2014 04:02 AM, Eduardo Habkost wrote:
> > This series is an attempt to make the compat_props lists from the PC code
> > reusable by other machine-types. All the compat bits that are on those
> > lists are
> > not tied
On Wed, Jun 11, 2014 at 01:55:01AM +0200, Fabian Aggeler wrote:
> Prepare for cp register banking by inserting every cp register twice,
> once for secure world and once for non-secure world.
Hi,
A question regarding the migration issue that Sergey raised.
Do we need to do anything about it or can
On Tue, Jun 24, 2014 at 03:02:03PM -0300, Eduardo Habkost wrote:
> The QEMU_COMPAT_* macros will contain compat properties that are not
> specific to PC, and may be reused by other machine-types.
>
> PC-specific properties were left on the PC_COMPAT_* macros.
>
> Signed-off-by: Eduardo Habkost
>
On Tue, Jun 24, 2014 at 03:02:02PM -0300, Eduardo Habkost wrote:
> The PC_COMPAT_* macros include each other, and the PC_Q35_COMPAT_*
> macros _also_ included each other. That caused lots of properties to
> appear multiple times on PC_Q35_COMPAT_*.
>
> For example, PC_Q35_COMPAT_1_4 expanded to th
On Tue, Jun 24, 2014 at 03:02:00PM -0300, Eduardo Habkost wrote:
> This series is an attempt to make the compat_props lists from the PC code
> reusable by other machine-types. All the compat bits that are on those lists
> are
> not tied to a specific machine-type, but instead to the device code th
On Tue, Jun 24, 2014 at 03:02:04PM -0300, Eduardo Habkost wrote:
> All compat properties are only applied if a device of an specific type
> is instantiated. There's no need to keep a PC-specific list of compat
> properties, as properties for PC-specific devices won't affect other
> machine-types an
Nikunj A Dadhania writes:
> Alexander Graf writes:
>
>> On 17.06.14 11:59, Nikunj A Dadhania wrote:
>>> Alexander Graf writes:
On 17.06.14 11:30, Nikunj A Dadhania wrote:
> Alexander Graf writes:
>
>>> +spapr_rtas_register("ibm,os-term", rtas_ibm_os_term);
>>> +spapr_r
On Wed, Jun 11, 2014 at 01:54:49AM +0200, Fabian Aggeler wrote:
> From: Sergey Fedorov
>
> This patch is based on idea found in patch at
> git://github.com/jowinter/qemu-trustzone.git
> f3d955c6c0ed8c46bc0eb10b634201032a651dd2 by
> Johannes Winter .
>
> This flag prevents QEMU from executing TCG
Every single sPAPR QOM object has small first "s".
Most (not all yet) QOM objects have "State" suffix.
This replaces SPAPRMachine with sPAPRMachineState to conform with QEMU
code style and removes redundant empty line.
Signed-off-by: Alexey Kardashevskiy
---
hw/ppc/spapr.c | 15 +++
This instruction space is guaranteed to be undefined.
ARM: 0111
Thumb: 1101 1110
The breakpoint instructions were selected from this instruction space.
Linux traps the illegal instruction and sends a SIGTRAP if it is a breakpoint.
Here is the Linux i
This adds a v2.1 machine to support backward compatibility
for newer macines in the case if they ever be implemented.
This adds a "pseries-2.1" machine as a child of the "pseries"
machine and only changes visible machine name.
Signed-off-by: Alexey Kardashevskiy
---
Changes:
v2:
* removed .insta
Add support for the SPLPAR Characteristics parameter to the emulated
RTAS call ibm,get-system-parameter.
The support provides just enough information to allow "cat
/proc/powerpc/lparcfg" to succeed without generating a kernel error
message.
Without this patch the above command will produce the fo
This series of patches improves QEMU's emulation of the RTAS call
"ibm,get-system-parameter" by adding support for the "UUID" and "SPLPAR
Characteristics" parameters as well as fixing a problem in the the
implementation of the "Platform Processor Diagnostics Run Mode" parameter.
It also improves
This allows the ibm,get-system-parameter RTAS call to succeed for the
DIAGNOSTICS_RUN_MODE system parameter.
The problem can be seen with "ppc64_cpu --run-mode" from the
powerpc-utils package which fails before this patch with "Machine does
not support diagnostic run mode".
This is corrected by u
Add a function to write lengh + data into a buffer as required for the
emulation of the RTAS ibm,get-system-parameter call.
If the destination is smaller than the source, the write is truncated
and success is returned. This matches the behaviour of pHyp.
This will be used in following patches.
S
Add support for the UUID parameter to the emulated RTAS call
ibm,get-system-parameter.
Return the guest's UUID as the value for the RTAS UUID system
parameter, or null (a zero length result) if it is not set.
Signed-off-by: Sam Bobroff
---
hw/ppc/spapr_rtas.c| 4
include/hw/ppc/spapr.h
Slow BAR access path is used when VFIO fails to mmap() BAR.
Since this is just a transport between the guest and a device, there is
no need to do endianness swapping.
This changes BARs to use native endianness. Since non-ROM BARs were
doing byte swapping, we need to remove it so does the patch.
As
On 24/06/14 22:06, Alexander Graf wrote:
>
> On 24.06.14 02:22, Sam Bobroff wrote:
>> This series of patches improves QEMU's emulation of the RTAS call
>> "ibm,get-system-parameter" by adding support for the "UUID" and "SPLPAR
>> Characteristics" parameters as well as fixing a problem in the the
>
On 06/24/2014 05:34 PM, Wenchao Xia wrote:
> This patch improves docs and address small issues in event
> callers.
>
> Signed-off-by: Wenchao Xia
> ---
> hw/watchdog/watchdog.c |2 +-
> include/block/blockjob.h |2 +-
> monitor.c|2 +-
> qapi-schema.json |
On 2014/5/19 19:22, Gerd Hoffmann wrote:
Hi,
I think '-vga none' just guarantees the qemu vga cards doesn't occupy
00:02.0, but this doesn't mean others use this specific slot since in
qemu internal, we always pass -1 to assign a slot automatically to
register a PCI device. So in some cases,
On 06/25/2014 04:02 AM, Eduardo Habkost wrote:
> This series is an attempt to make the compat_props lists from the PC code
> reusable by other machine-types. All the compat bits that are on those lists
> are
> not tied to a specific machine-type, but instead to the device code that was
> present o
On 06/24/2014 05:33 PM, Wenchao Xia wrote:
> This patch improve docs and uses c_type(argentry, is_param=True)
> in script.
>
> Signed-off-by: Wenchao Xia
> ---
> docs/qapi-code-gen.txt |8
> scripts/qapi-event.py |5 ++---
> scripts/qapi.py
On 2014/6/24 10:59, Zhenyu Wang wrote:
On 2014.06.19 17:53:51 +0800, Tiejun Chen wrote:
Originally the reason to probe ISA bridge instead of Dev31:Fun0
is to make graphics device passthrough work easy for VMM, that
only need to expose ISA bridge to let driver know the real
hardware underneath. T
Implement that pci host bridge to specific to passthrough. Actually
this just inherit the standard one.
Signed-off-by: Tiejun Chen
---
v5:
* Nothing is changed.
v4:
* Fix one typo in the patch head description.
* Use (xen_enabled() && xen_has_gfx_passthru) to make sure we only work
in this s
ISA bridge is needed since Intel gfx drive will probe with Dev31:Fun0
to make graphics device passthrough work well for VMM, that only need
to expose this pseudo ISA bridge to let driver know the real hardware
underneath.
The original patch is from Allen Kay
Signed-off-by: Yang Zhang
Signed-off
On 06/24/2014 05:33 PM, Wenchao Xia wrote:
> Signed-off-by: Wenchao Xia
> ---
> .gitignore |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Reviewed-by: Eric Blake
>
> diff --git a/.gitignore b/.gitignore
> index c658613..2286d0a 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -
Some registers of Intel IGD are mapped in host bridge, so it needs to
passthrough these registers of physical host bridge to guest because
emulated host bridge in guest doesn't have these mappings.
The original patch is from Weidong Han
Signed-off-by: Yang Zhang
Signed-off-by: Tiejun Chen
Cc:
The OpRegion shouldn't be mapped 1:1 because the address in the host
can't be used in the guest directly.
This patch traps read and write access to the opregion of the Intel
GPU config space (offset 0xfc).
The original patch is from Jean Guyader
Signed-off-by: Yang Zhang
Signed-off-by: Tiejun
basic gfx passthrough support:
- add a vga type for gfx passthrough
- retrieve VGA bios from sysfs, then load it to guest at 0xC
- register/unregister legacy VGA I/O ports and MMIOs for passthrough GFX
The original patch is from Weidong Han
Signed-off-by: Yang Zhang
Signed-off-by: Tiejun Ch
V5 is generated just based on Paolo's some comments.
v5:
* Don't set that ISA class property, instead, just fake this ISA bridge
with 00:1f.0.
* Don't pass vendor/device ids in igd_pci_read().
* Add to support offset 0x44/0x48.
* Just rebase.
v4:
* Fix some typos in the patch head description
On 06/24/2014 05:33 PM, Wenchao Xia wrote:
> Signed-off-by: Wenchao Xia
> ---
> Makefile |2 +-
> qapi-event.json | 318
> --
> qapi-schema.json |5 +-
> qapi/event.json | 318
> +
On 06/24/2014 06:08 PM, Xiongzi Ge wrote:
> Hi Eric,
[we tend to avoid top-posting on technical lists]
>
> This really works if I set up the same configuration (/dev/vda in the
> guest) but the physical block devices are not the same after migration.The
> ABI is the same. When the guest cache s
This series is an attempt to make the compat_props lists from the PC code
reusable by other machine-types. All the compat bits that are on those lists are
not tied to a specific machine-type, but instead to the device code that was
present on a given QEMU version.
This series is based on Michael's
The QEMU_COMPAT_* macros will contain compat properties that are not
specific to PC, and may be reused by other machine-types.
The compat properties for PC-specific devices were moved to
QEMU_COMPAT_* too, because they are simply not going to be applied to
any device if they are not instantiated.
For each compat property on PC_Q35_COMPAT_*, there are only two
possibilities:
* If the device is never instantiated when using a machine other than
pc-q35, then the compat property can be safely added to
PC_COMPAT_*;
* If the device can be instantiated when using a machine other than
p
On Tue, Jun 24, 2014 at 02:55:20PM -0300, Eduardo Habkost wrote:
> On Tue, Jun 24, 2014 at 05:47:53PM +0100, Peter Maydell wrote:
> > On 24 June 2014 17:44, Eduardo Habkost wrote:
> > > (I would go even further and say that no compat_props bit need to be
> > > specific to a machine-type family, an
This patch adds a new subtest, it hotplugs 29 * 8 = 232 virtio-blk
devices to guest, and try to hot-unplug them.
Note: the hot-unplug can't work without cooperation of guest OS.
Signed-off-by: Amos Kong
---
tests/virtio-blk-test.c | 68 +
1 file c
I want to add a new subtest in virtio-blk-test, it will start
guest without network. The original pci_init() did nothing, but
it's good to reserve a very simple initialization testing.
Signed-off-by: Amos Kong
Reviewed-by: Stefan Hajnoczi
---
tests/virtio-blk-test.c | 13 ++---
1 file c
It's worth to add a hotplug test to qtest, but without
cooperation of guest OS, new devices can't be initialized
by guest, and hot-unplug doesn't work.
However, the new test can cover some part of code of
hotplug/unplug.
I will write another subtest to test hotplug with pci support.
V2: move qmp
This patch wraps a helper function to execute human command by
one QMP command (human-monitor-command). It also checks the return
string.
Signed-off-by: Amos Kong
---
tests/libqtest.c | 23 +++
tests/libqtest.h | 9 +
2 files changed, 32 insertions(+)
diff --git a/t
Signed-off-by: Amos Kong
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Andreas Färber
---
tests/blockdev-test.c | 23 ++-
1 file changed, 2 insertions(+), 21 deletions(-)
diff --git a/tests/blockdev-test.c b/tests/blockdev-test.c
index c940e00..c9127c0 100644
--- a/tests/blockd
On Fri, Jun 13, 2014 at 10:15:00AM +0200, Paolo Bonzini wrote:
> libqtest is using g_strdup_printf to format QMP commands, but
> this does not work if the argument strings need to be escaped.
> Instead, use the fancy %-formatting functionality of QObject.
> The only change required in tests is that
On 05/30/2014 11:45 PM, Alexander Graf wrote:
>
> On 30.05.14 15:36, Alexey Kardashevskiy wrote:
>> On 05/30/2014 08:08 PM, Alexander Graf wrote:
>>> On 30.05.14 11:34, Alexey Kardashevskiy wrote:
Currently SPAPR PHB keeps track of all allocated MSI (here and below
MSI stands for both MS
On Tue, Jun 24, 2014 at 11:30:04PM +0100, Peter Maydell wrote:
> On 24 June 2014 18:55, Eduardo Habkost wrote:
> > On Tue, Jun 24, 2014 at 05:47:53PM +0100, Peter Maydell wrote:
> >> What if different machines in a particular release had the
> >> property set to different defaults?
> >
> > I never
Hi Eric,
This really works if I set up the same configuration (/dev/vda in the
guest) but the physical block devices are not the same after migration.The
ABI is the same. When the guest cache stores a page like 'aaa' which is in
the block device of Host A. If the cache in the guest is also migrat
On Tue, Jun 24, 2014 at 04:43:23PM +0200, Alexander Graf wrote:
>
>On 10.06.14 04:03, Gavin Shan wrote:
>>The emulation for EEH RTAS requests from guest isn't covered
>>by QEMU yet and the patch implements them.
>>
>>The patch defines constants used by EEH RTAS calls and adds
>>callback sPAPRPHBCla
Signed-off-by: Wenchao Xia
---
.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/.gitignore b/.gitignore
index c658613..2286d0a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -26,6 +26,7 @@
/qapi-generated
/qapi-types.[ch]
/qapi-visit.[ch]
+/qapi-event.[ch]
/qmp
This patch improves docs and address small issues in event
callers.
Signed-off-by: Wenchao Xia
---
hw/watchdog/watchdog.c |2 +-
include/block/blockjob.h |2 +-
monitor.c|2 +-
qapi-schema.json |7 ---
qapi/block-core.json |3 ++-
qapi/event.
Paolo Bonzini (1):
tests/test-qmp-event: fix for GLib < 2.31
Wenchao Xia (4):
qapi: move event defines
qapi: ignore generated event files
qapi script: clean up in scripts
qapi event: clean up in callers
.gitignore |1 +
Makefile
From: Paolo Bonzini
On old GLib, the test needs a g_thread_init call.
Reported-by: Wenchao Xia
Signed-off-by: Paolo Bonzini
Tested-by: Wenchao Xia
Signed-off-by: Wenchao Xia
---
tests/test-qmp-event.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/tests/test-qmp-ev
Signed-off-by: Wenchao Xia
---
Makefile |2 +-
qapi-event.json | 318 --
qapi-schema.json |5 +-
qapi/event.json | 318 ++
4 files changed, 322 insertions(+), 321 deletions(
This patch improve docs and uses c_type(argentry, is_param=True)
in script.
Signed-off-by: Wenchao Xia
---
docs/qapi-code-gen.txt |8
scripts/qapi-event.py |5 ++---
scripts/qapi.py |2 +-
tests/qapi-schema/event-nes
On 06/24/2014 04:06 PM, Peter Lieven wrote:
> upcoming libnfs will feature internal readahead support.
> Add a knob to pass the optional readahead value as a URL
> parameter.
>
> Signed-off-by: Peter Lieven
> ---
> block/nfs.c |4
> 1 file changed, 4 insertions(+)
Reviewed-by: Eric Bla
On 06/24/2014 04:06 PM, Peter Lieven wrote:
> this patch fixes the incorrect usage of strncmp and
> adds simple error checking by means of parse_uint_full
> instead of atoi for the supplied URL parameters.
>
> Signed-off-by: Peter Lieven
> ---
> block/nfs.c | 18 --
> 1 file ch
On 06/24/2014 03:55 PM, Marcelo Tosatti wrote:
>
> It is necessary to reset RTC interrupt reinjection backlog if
> guest time is synchronized via a different mechanism, such as
> QGA's guest-set-time command.
>
> Failing to do so causes both corrections to be applied (summed),
> resulting in an i
On 06/24/2014 03:29 PM, Brian Jackson wrote:
>
>
> On 6/24/2014 2:22 PM, Xiongzi Ge wrote:
>> Hi,
>>
>>
>> When I do live migration, in the source and destination host, there are
>> different block devices, but qemu can not detect this. I used virtio
>> as the
>> driver in kvm and in the vdi devi
On Wed, Jun 25, 2014 at 8:39 AM, Alistair Francis
wrote:
> On Wed, Jun 25, 2014 at 1:55 AM, Christopher Covington
> wrote:
>> On 06/23/2014 09:12 PM, Alistair Francis wrote:
>>> Call the new pmccntr_sync() function when there is a possibility
>>> of swapping ELs (I.E. when there is an exception)
On Tue, Jun 24, 2014 at 10:58:29PM +0200, BALATON Zoltan wrote:
> On Tue, 24 Jun 2014, Eduardo Habkost wrote:
[...]
> >+.driver = "pci-serial",\
> >+.property = "prog_if",\
> >+.value= stringify(0),\
> >+},\
> >+{\
> >+.driver = "pci-serial-2x",\
> >+
The property name is "prog_if", not "prof_if".
Signed-off-by: Eduardo Habkost
Cc: BALATON Zoltan
---
include/hw/i386/pc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
index 486e98f..1331d5a 100644
--- a/include/hw/i386/pc.h
+++
On 24.06.14 19:59, Madhavan Srinivasan wrote:
On Tuesday 24 June 2014 10:36 PM, bharat.bhus...@freescale.com wrote:
-Original Message-
From: Madhavan Srinivasan [mailto:ma...@linux.vnet.ibm.com]
Sent: Tuesday, June 24, 2014 8:59 PM
To: Bhushan Bharat-R65777; ag...@suse.de
Cc: qemu-...
On 24.06.14 18:57, bharat.bhus...@freescale.com wrote:
-Original Message-
From: Alexander Graf [mailto:ag...@suse.de]
Sent: Tuesday, June 24, 2014 8:21 PM
To: Bhushan Bharat-R65777
Cc: qemu-...@nongnu.org; qemu-devel@nongnu.org; ma...@linux.vnet.ibm.com
Subject: Re: [PATCH 5/5 v3][RESE
On Wed, Jun 25, 2014 at 1:56 AM, Peter Maydell wrote:
> On 24 June 2014 02:12, Alistair Francis wrote:
>> +/* This implements the PMCCFILTR_EL0:P and U bits; the PMXEVTYPER:P and
>> U
>> + * bits and the c9_pmcr:E bit.
>> + *
>> + * It does not suppor the secure/non-secure compon
On Wed, Jun 25, 2014 at 1:31 AM, Christopher Covington
wrote:
> Hi Alistair,
>
> On 06/23/2014 09:12 PM, Alistair Francis wrote:
>> Include a helper function to determine if the CCNT counter
>> is enabled as well as the constants used to mask the pmccfiltr_el0
>> register.
>>
>> Signed-off-by: Ali
On Wed, Jun 25, 2014 at 1:55 AM, Christopher Covington
wrote:
> On 06/23/2014 09:12 PM, Alistair Francis wrote:
>> Call the new pmccntr_sync() function when there is a possibility
>> of swapping ELs (I.E. when there is an exception)
>>
>> Signed-off-by: Alistair Francis
>> ---
>>
>> target-arm/h
On Wed, Jun 25, 2014 at 1:35 AM, Christopher Covington
wrote:
> On 06/23/2014 09:12 PM, Alistair Francis wrote:
>> This is used to synchronise the PMCCNTR counter and swap its
>> state between enabled and disabled if required. It must always
>> be called twice, both before and after any logic that
On 24 June 2014 18:55, Eduardo Habkost wrote:
> On Tue, Jun 24, 2014 at 05:47:53PM +0100, Peter Maydell wrote:
>> What if different machines in a particular release had the
>> property set to different defaults?
>
> I never saw that happen, and I don't think it is even likely: default
> values set
Tested-by: Wenchao Xia
upcoming libnfs will feature internal readahead support.
Add a knob to pass the optional readahead value as a URL
parameter.
Signed-off-by: Peter Lieven
---
block/nfs.c |4
1 file changed, 4 insertions(+)
diff --git a/block/nfs.c b/block/nfs.c
index 0b44483..8439e0d 100644
--- a/block/
upcoming libnfs will feature internal readahead support.
Add a knob to pass the optional readahead value as a URL
parameter.
This series fixes also the incorrect usage of strncmp and
atoi.
v2->v3: - use parse_uint_full [Eric]
- split patch [Eric]
v1->v2: use strtol instead of atoi [Eric]
this patch fixes the incorrect usage of strncmp and
adds simple error checking by means of parse_uint_full
instead of atoi for the supplied URL parameters.
Signed-off-by: Peter Lieven
---
block/nfs.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/block/
It is necessary to reset RTC interrupt reinjection backlog if
guest time is synchronized via a different mechanism, such as
QGA's guest-set-time command.
Failing to do so causes both corrections to be applied (summed),
resulting in an incorrect guest time.
Signed-off-by: Marcelo Tosatti
diff -
Am 24.06.2014 18:04, schrieb Eric Blake:
> On 06/24/2014 02:52 AM, Peter Lieven wrote:
>> upcoming libnfs will feature internal readahead support.
>> Add a knob to pass the optional readahead value as a URL
>> parameter.
>>
>> This patch fixes also the incorrect usage of strncmp and
>> atoi.
>>
>>
On 06/24/2014 05:26 PM, Xiongzi Ge wrote:
> Hi ,
>
> This is just related to migration, but it may be not in the standard
> migration. The cache device in different hosts can only be accessed by the vm
> running in the host. The problem for me is to find the interface of the cache
> in the guest
On 06/24/2014 02:24 PM, Al Viro wrote:
> Al, off to figure out the black magic TCG is using to generate calls...
If you've a helper
DEF_HELPER_1(halt, void, i64)
then
gen_helper_halt(...)
will generate the tcg ops that result in the call.
r~
Any news on this?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323758
Title:
Mouse stops working when connected usb-storage-device
Status in QEMU:
New
Status in “qemu” package in Ubuntu:
New
On 6/24/2014 2:22 PM, Xiongzi Ge wrote:
Hi,
When I do live migration, in the source and destination host, there are
different block devices, but qemu can not detect this. I used virtio as the
driver in kvm and in the vdi device in the guest is /dev/vda. So, the vm
guest can read different d
Hi ,
This is just related to migration, but it may be not in the standard
migration. The cache device in different hosts can only be accessed by the
vm running in the host. The problem for me is to find the interface of the
cache in the guest or like first doing it in the qemu, after migration,
On Tue, Jun 24, 2014 at 01:57:52PM -0700, Richard Henderson wrote:
> On 06/24/2014 01:32 PM, Al Viro wrote:
> > If you have any ideas for testing, I do have working hw (the box that is
> > currently alive is ev45, though; I _can_ try to boot a UP1000 one, but
> > I make no promises regarding its fa
1 - 100 of 360 matches
Mail list logo
