On Tue, Jan 31, 2012 at 8:34 AM, Matt Evans m...@ozlabs.org wrote:
+#define DEBUG_SPAPR_HCALLS
I suppose this shouldn't be defined by default?
+#ifdef DEBUG_SPAPR_HCALLS
+#define hcall_dprintf(fmt, ...) \
+ do { fprintf(stderr, fmt, ## __VA_ARGS__); } while (0)
+#else
+#define
On Tue, Jan 31, 2012 at 8:30 AM, Matt Evans m...@ozlabs.org wrote:
Commit d3923126a24212f1e746a84a575dadbd9f259418 added a bunch of
nice error checking around ioevent__init() but the init may gracefully
fail if ioevents simply aren't supported (PPC64 KVM).
This commit adds a new return code
On Tue, Jan 31, 2012 at 8:34 AM, Matt Evans m...@ozlabs.org wrote:
This series adds support for a PPC64 platform, SPAPR, on top of the previous
more general PPC64 CPU support. This platform is paravirtualised, with most
of the MMU hypercalls being dealt with in the kernel. Userland needs to
On 01/31/2012 03:17 AM, Takuya Yoshikawa wrote:
Added s390 and ppc developers to Cc,
(2012/01/30 14:35), Takuya Yoshikawa wrote:
Some members of kvm_memory_slot are not used by every architecture.
This patch is the first step to make this difference clear by
introducing
(2012/01/31 18:18), Avi Kivity wrote:
On 01/31/2012 03:17 AM, Takuya Yoshikawa wrote:
Added s390 and ppc developers to Cc,
(2012/01/30 14:35), Takuya Yoshikawa wrote:
Some members of kvm_memory_slot are not used by every architecture.
This patch is the first step to make this difference
On Mon, Jan 30, 2012 at 04:26:06PM +0100, Kevin Wolf wrote:
Would that be enough or would we have to avoid clearing it in all other
places as well? Where would it be initialised if it's not enough?
Maybe vmx_vcpu_reset().
Do all CPL changes go through set_cr0/segment/rflags/cpl? I
https://bugzilla.kernel.org/show_bug.cgi?id=42563
--- Comment #8 from Gleb g...@redhat.com 2012-01-31 09:39:50 ---
(In reply to comment #7)
(In reply to comment #6)
(In reply to comment #5)
(In reply to comment #4)
Yes. With 'ignore_msrs=y' added when loading kvm module,
https://bugzilla.kernel.org/show_bug.cgi?id=42563
Jay Ren yongjie@intel.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=42563
Jay Ren yongjie@intel.com changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--
https://bugzilla.kernel.org/show_bug.cgi?id=42563
Jay Ren yongjie@intel.com changed:
What|Removed |Added
Status|VERIFIED|CLOSED
--- Comment #9
On 31 Jan 2012, at 18:59, Pekka Enberg wrote:
On Tue, Jan 31, 2012 at 8:34 AM, Matt Evans m...@ozlabs.org wrote:
+static struct cpu_info cpu_power7_info = {
+ POWER7,
+ power7_page_sizes_prop, sizeof(power7_page_sizes_prop),
+ power7_segment_sizes_prop,
On 31 Jan 2012, at 19:11, Pekka Enberg wrote:
On Tue, Jan 31, 2012 at 8:34 AM, Matt Evans m...@ozlabs.org wrote:
+#define DEBUG_SPAPR_HCALLS
I suppose this shouldn't be defined by default?
Well, I had a bit of a debate about it. I left it on as it is actually
interesting whilst
On 01/31/2012 11:37 AM, Gleb Natapov wrote:
On Mon, Jan 30, 2012 at 04:26:06PM +0100, Kevin Wolf wrote:
Would that be enough or would we have to avoid clearing it in all other
places as well? Where would it be initialised if it's not enough?
Maybe vmx_vcpu_reset().
Do all CPL
Hi All,
In my development I came across the state where I need more than 32 kvmslots
QEMU/kvm-all.c:
cut
struct KVMState
{
KVMSlot slots[32];
cut
Followings are the solution I thought of:
Solution 1:
Increase the slot to 64 in both KVM and QEMU. I think this will also
(added KVM folks to the Cc:)
* Bastien ROUCARIES roucaries.bast...@gmail.com wrote:
Ping^2
Bastien
On Mon, Jan 23, 2012 at 11:28 AM, Bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
On Mon, Jan 16, 2012 at 8:21 PM, H. Peter Anvin h...@zytor.com wrote:
On 01/16/2012 03:27 AM,
On 01/31/2012 05:35 AM, Zhi Yong Wu wrote:
HI,
Can anyone let me know know the difference between VMXON region and
VMCS region? relationship?
There is no relationship between them:
VMXON region is created per logical processor and used by it for VMX ops.
VMCS region is created for each
On 01/28/2012 04:21 PM, Alex Williamson wrote:
To date we've only exposed BARs as 32bit even if the device
physically supports 64bit BARs. Enable 64bit BARs to be
exposed as such in the guest, which may free up MMIO below
4G should the guest choose to use it.
This adds a new mem64= option
Christian Borntraeger borntrae...@de.ibm.com wrote:
Some members of kvm_memory_slot are not used by every architecture.
This patch is the first step to make this difference clear by
introducing kvm_memory_slot::arch; lpage_info is moved into it.
Patch series seems to work on s390.
On 2012-01-31 13:40, Avi Kivity wrote:
On 01/28/2012 04:21 PM, Alex Williamson wrote:
To date we've only exposed BARs as 32bit even if the device
physically supports 64bit BARs. Enable 64bit BARs to be
exposed as such in the guest, which may free up MMIO below
4G should the guest choose to
On 01/28/2012 04:21 PM, Alex Williamson wrote:
Stop using compatibility mode and at the same time fix available
access sizes. The PCI spec indicates that the MSI-X table may
only be accessed as DWORD or QWORD.
static const MemoryRegionOps msix_mmio_ops = {
-.old_mmio = {
-
On 01/28/2012 04:22 PM, Alex Williamson wrote:
We currently only update MSI-X configuration with the enable bit
in PCI config space is toggled. This is pretty sketchy and part
of the reason for the odd checks for vector data is to guess
whether the guest is going to use the vector so we can
On 01/31/2012 02:45 PM, Jan Kiszka wrote:
On 2012-01-31 13:40, Avi Kivity wrote:
On 01/28/2012 04:21 PM, Alex Williamson wrote:
To date we've only exposed BARs as 32bit even if the device
physically supports 64bit BARs. Enable 64bit BARs to be
exposed as such in the guest, which may free
On 01/30/2012 03:44 PM, Alex Williamson wrote:
On Mon, 2012-01-30 at 11:11 +0100, Jan Kiszka wrote:
On 2012-01-28 15:21, Alex Williamson wrote:
Patch 1 2 here are independent of the rest, but I include them
here to avoid conflicts. The first patch enables exposing MMIO
BARs as their
On 2012-01-31 13:52, Avi Kivity wrote:
On 01/30/2012 03:44 PM, Alex Williamson wrote:
On Mon, 2012-01-30 at 11:11 +0100, Jan Kiszka wrote:
On 2012-01-28 15:21, Alex Williamson wrote:
Patch 1 2 here are independent of the rest, but I include them
here to avoid conflicts. The first patch
On 2012-01-31 13:51, Avi Kivity wrote:
On 01/31/2012 02:45 PM, Jan Kiszka wrote:
On 2012-01-31 13:40, Avi Kivity wrote:
On 01/28/2012 04:21 PM, Alex Williamson wrote:
To date we've only exposed BARs as 32bit even if the device
physically supports 64bit BARs. Enable 64bit BARs to be
exposed
On 01/31/2012 02:57 PM, Jan Kiszka wrote:
Seems fine, but do we really need the option? If it doesn't work we
should treat it as an ordinary but and fix it.
So far it's against the architecture of the emulated system: our current
chipset predates 64 bit PCI.
Then it should be
Am 31.01.2012 00:53, schrieb Anthony Liguori:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
VMState:
Anthony specifically said that VMState were not affected by QOM and that
patches
On 2012-01-31 14:10, Avi Kivity wrote:
On 01/31/2012 02:57 PM, Jan Kiszka wrote:
Seems fine, but do we really need the option? If it doesn't work we
should treat it as an ordinary but and fix it.
So far it's against the architecture of the emulated system: our current
chipset predates 64
On 01/31/2012 03:21 PM, Jan Kiszka wrote:
On 2012-01-31 14:10, Avi Kivity wrote:
On 01/31/2012 02:57 PM, Jan Kiszka wrote:
Seems fine, but do we really need the option? If it doesn't work we
should treat it as an ordinary but and fix it.
So far it's against the architecture of the
On Tue, 2012-01-31 at 17:30 +1100, Matt Evans wrote:
Commit d3923126a24212f1e746a84a575dadbd9f259418 added a bunch of
nice error checking around ioevent__init() but the init may gracefully
fail if ioevents simply aren't supported (PPC64 KVM).
This commit adds a new return code for the init
On 01/31/2012 03:32 PM, Peter Zijlstra wrote:
Subject: srcu: Implement call_srcu()
From: Peter Zijlstra a.p.zijls...@chello.nl
Date: Mon Jan 30 23:20:49 CET 2012
Implement call_srcu() by using a state machine driven by
call_rcu_sched() and timer callbacks.
The state machine is a direct
On Tue, 2012-01-31 at 15:47 +0200, Avi Kivity wrote:
They really need to return quickly to userspace, and they really need to
perform some operation between rcu_assign_pointer() and returning, so no.
Bugger :/
Compile tested only!! :-)
How much did synchronize_srcu_expedited()
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
QOM roadmap update:
* Series 3/4 is on the list.
- Please officially designate a merge date (Friday?).
- To make review sensible, I ask
On 01/31/2012 05:15 PM, Andreas Färber wrote:
Am 31.01.2012 00:53, schrieb Anthony Liguori:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
VMState:
Anthony specifically said that
Hi,
We are setting up a ubuntu / openstack / KVM based private cloud. Of the 3
servers involved in this configuration 1 has been crashing frequently over the
last month.
Since it is the only server responsible for the virtualization (so the only one
running kvm virtual machines) my guess was
On 01/31/2012 03:59 PM, Anthony Liguori wrote:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
QOM roadmap update:
* Series 3/4 is on the list.
- Please officially designate a merge
On 01/31/2012 07:15 AM, Andreas Färber wrote:
Am 31.01.2012 00:53, schrieb Anthony Liguori:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
VMState:
Anthony specifically said that
On 01/31/2012 08:09 AM, Avi Kivity wrote:
On 01/31/2012 03:59 PM, Anthony Liguori wrote:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
QOM roadmap update:
* Series 3/4 is on the list.
On 01/31/2012 04:06 PM, Bram De Wilde wrote:
Hi,
We are setting up a ubuntu / openstack / KVM based private cloud. Of the 3
servers involved in this configuration 1 has been crashing frequently over
the last month.
Since it is the only server responsible for the virtualization (so the only
On 01/30/2012 11:46 PM, Peter Maydell wrote:
On 20 January 2012 02:59, Christoffer Dall
c.d...@virtualopensystems.com wrote:
There's a new list of issues available at:
https://github.com/virtualopensystems/linux-kvm-arm/issues
Thanks for putting this up. Here's a couple more for you :-)
*
Add a check on the base VM class for illegal
instruction code executed by the VM. That
check is performed on the serial console
output.
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/virt/virt_vm.py | 27 +++
1 files changed, 27 insertions(+), 0 deletions(-)
The patch solve problem with doubled name of cpuflags
sse4_1, sse4.1 etc. in cpuflag test.
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/virt/virt_utils.py | 14 --
1 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/client/virt/virt_utils.py
We had migration_control.srv which worked with old
version of kvm config files (tests.cfg, subtest.cfg,
etc..). Because config files were changed this control
code stopped working.
This patch repairs this problem and renames the file
to the more correct and generic name multi-host.srv.
Also,
Signed-off-by: Jiří Župka jzu...@redhat.com
---
client/tests/kvm/tests/cpuflags.py | 284 +++-
client/virt/subtests.cfg.sample| 17 ++-
2 files changed, 263 insertions(+), 38 deletions(-)
diff --git a/client/tests/kvm/tests/cpuflags.py
On 01/31/2012 04:17 PM, Anthony Liguori wrote:
On 01/31/2012 08:09 AM, Avi Kivity wrote:
On 01/31/2012 03:59 PM, Anthony Liguori wrote:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
On Tue, Jan 31, 2012 at 08:12:29AM -0600, Anthony Liguori wrote:
On 01/31/2012 07:15 AM, Andreas Färber wrote:
Am 31.01.2012 00:53, schrieb Anthony Liguori:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are
On Tue, Jan 31, 2012 at 05:04:48PM +0200, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 08:12:29AM -0600, Anthony Liguori wrote:
On 01/31/2012 07:15 AM, Andreas Färber wrote:
Am 31.01.2012 00:53, schrieb Anthony Liguori:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012
On 01/31/2012 03:12 PM, Anthony Liguori wrote:
Don't use VMState. Just open code a save/restore function. VMState is
too limited in how it handles complex data structures.
I really believe the only long term solution we're going to get to here
is something that uses a builder interface (like
Now that we have a flag that will tell the guest it was suspended, create an
interface for that communication using a KVM ioctl.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc: mi...@redhat.com
Cc: h...@zytor.com
Cc: ry...@linux.vnet.ibm.com
Cc: aligu...@us.ibm.com
Cc: mtosa...@redhat.com
Cc:
This flag will be used to check if the vm was stopped by the host when a soft
lockup was detected. The host will set the flag when it stops the guest. On
resume, the guest will check this flag if a soft lockup is detected and skip
issuing the warning.
Signed-off-by: Eric B Munson
A suspended VM can cause spurious soft lockup warnings. To avoid these, the
watchdog now checks if the kernel knows it was stopped by the host and skips
the warning if so. When the watchdog is reset successfully, clear the guest
paused flag.
Signed-off-by: Eric B Munson emun...@mgebm.net
Cc:
When a host stops or suspends a VM it will set a flag to show this. The
watchdog will use these functions to determine if a softlockup is real, or the
result of a suspended VM.
Signed-off-by: Eric B Munson emun...@mgebm.net
asm-generic changes Acked-by: Arnd Bergmann a...@arndb.de
Cc:
Changes from V10:
Return ioctl to per vcpu instead of per vm
Changes from V9:
Use kvm_for_each_vcpu to iterate online vcpu's
Changes from V8:
Make KVM_GUEST_PAUSED a per vm ioctl instead of per vcpu
Changes from V7:
Define KVM_CAP_GUEST_PAUSED and support check
Call mark_page_dirty () after
On Tue, Jan 24, 2012 at 03:06:05PM +0200, Gleb Natapov wrote:
The spec says that during initialization The edge sense circuit is
reset which means that following initialization an interrupt request
(IR) input must make a low-to-high transition to generate an interrupt,
but currently if edge
Am 31.01.2012 14:59, schrieb Anthony Liguori:
On 01/30/2012 05:41 PM, Andreas Färber wrote:
Am 30.01.2012 19:55, schrieb Juan Quintela:
Please send in any agenda items you are interested in covering.
QOM roadmap update:
* Series 3/4 is on the list.
- Please officially designate a merge
https://bugzilla.kernel.org/show_bug.cgi?id=42703
Summary: random hangs on virtualization host
Product: Virtualization
Version: unspecified
Kernel Version: 3.0.0-16
Platform: All
OS/Version: Linux
Tree: Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=42703
Avi Kivity a...@redhat.com changed:
What|Removed |Added
CC||a...@redhat.com
Le Mon, Jan 30, 2012 at 07:21:20PM +0200, Avi Kivity ecrivait :
Start with top and vmstat to see if the cpu or I/O are the bottleneck
with top at the kvm layer, the VM take 50% of CPU (the physical
box have 16 real cores-not HT- : AMD Opteron 6134).
one result of vmstat :
What's up with the cc list?
On 01/31/2012 07:15 PM, David Cure wrote:
Le Mon, Jan 30, 2012 at 07:21:20PM +0200, Avi Kivity ecrivait :
Start with top and vmstat to see if the cpu or I/O are the bottleneck
with top at the kvm layer, the VM take 50% of CPU (the physical
box have 16
Avoid changing the IRQ level to high on reset as it may trigger spurious
events. Instead, open-code the effects of pit_load_count(0) in the reset
handler.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/i8254.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output level and applies it when legacy
mode is turned off again. This value has to be preserved across save/
restore as it cannot be reconstructed otherwise.
Signed-off-by: Jan Kiszka
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at this chance.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
arch_init.c|1 +
hw/i82378.c|3 +-
hw/mips_jazz.c |3 +-
hw/pc.c|3 +-
hw/pc.h|
HPET legacy emulation will require control over the PIT IRQ output. To
enable this, add support for an alternative IRQ output object to the PIT
factory function. If the isa_irq number is 0, this object will be
used.
This also removes the IRQ number property from the PIT class as we now
use a
Instead of providing 4 individual query functions for mode, gate, output
and initial counter state, introduce a service that queries all
information at once. This comes with tiny additional costs for
pcspk_callback but with a much cleaner interface. Also, it will simplify
the implementation of the
This is a preparatory series to allow the introduction of the KVM
in-kernel PIT. It also fixes various bugs in the PIT and HPET code,
see patches for details.
Changes in V3:
- rebased over master
- tuned pic_init interface to avoid isa_get_irq(NULL, ...)
Jan Kiszka (7):
i8254: Do not raise
When the HPET enters legacy mode, the IRQ output of the PIT is
suppressed and replaced by the HPET timer 0. But the current code to
emulate this was broken in many ways. It reset the PIT state after
re-enabling, it worked against a stale static PIT structure, and it did
not properly saved/restored
Move the public interface of the PIT into its own header file and update
all users.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/alpha_dp264.c |1 +
hw/hpet.c |1 +
hw/i82378.c|1 +
hw/i8254.c |1 +
hw/i8254.h | 54
To both avoid that kvm_irqchip_in_kernel always has to be paired with
kvm_enabled and that the former ends up in a function call, implement it
like the latter. This means keeping the state in a global variable and
defining kvm_irqchip_in_kernel as a preprocessor macro.
Signed-off-by: Jan Kiszka
This provides the required user space stubs to enable the in-kernel
i8254 emulation of KVM.
The in-kernel model supports lost tick compensation according to the
delay policy. This is enabled by default and can be switched off via a
device property.
Depending on the feature set of the host kernel
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming KVM in-kernel version. We share most of the
public interface of the i8254, specifically to the pcspk, vmstate, reset
and certain init
To be used for in-kernel PIT emulation.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c | 10 ++
kvm-stub.c |5 +
kvm.h |1 +
3 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index 3f2460f..8df5235 100644
---
This adds another piece of qemu-kvm to upstream: The accelerated
in-kernel model of the i8254. It does this in the same fashion as the
interrupt controllers were already introduced. And it even has one bug
less than qemu-kvm: PC speaker output still works with KVM acceleration
enabled.
The
Same as for the APIC: To enable migration between accelerated and
non-accelerated models, we need to arm the channel 0 timer only inside
the emulated PIT model. The common code just saves/restores that timer
to the the next_transition_time field.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:22:09AM -0700, Alex Williamson wrote:
Per the PCI spec, all vectors should be masked at handoff.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/device-assignment.c | 20
On Sat, Jan 28, 2012 at 07:22:09AM -0700, Alex Williamson wrote:
Per the PCI spec, all vectors should be masked at handoff.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/device-assignment.c | 20 +++-
1 files changed, 19 insertions(+), 1 deletions(-)
On Sat, Jan 28, 2012 at 07:21:58AM -0700, Alex Williamson wrote:
This makes access much easier.
Signed-off-by: Alex Williamson alex.william...@redhat.com
Yes but this also makes it easier to forget
to handle endian-ness.
How about using pci_get/pci_set instead?
---
On Mon, Jan 30, 2012 at 02:05:54PM -0700, Alex Williamson wrote:
We need to prioritize our matching when setting MSI-X vector
entries. Unused entries should only be used if we don't find
an exact match or else we risk duplicating entries. This was
causing an ENOSPC return when trying to mask
On Tue, Jan 31, 2012 at 12:07:39PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:22:09AM -0700, Alex Williamson wrote:
Per the PCI spec, all vectors should be masked at handoff.
Signed-off-by: Alex Williamson
On 2012-01-31 20:12, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 12:07:39PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:22:09AM -0700, Alex Williamson wrote:
Per the PCI spec, all vectors should be masked at
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:21:58AM -0700, Alex Williamson wrote:
This makes access much easier.
Signed-off-by: Alex Williamson alex.william...@redhat.com
Yes but this also makes it easier to forget
to handle endian-ness.
How
On Tue, Jan 31, 2012 at 12:05:49PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:21:58AM -0700, Alex Williamson wrote:
This makes access much easier.
Signed-off-by: Alex Williamson alex.william...@redhat.com
On Tue, Jan 31, 2012 at 11:47:32AM +, Bhushan Bharat-R65777 wrote:
Hi All,
In my development I came across the state where I need more than 32 kvmslots
QEMU/kvm-all.c:
cut
struct KVMState
{
KVMSlot slots[32];
cut
Followings are the solution I thought of:
On Sat, Jan 28, 2012 at 07:22:04AM -0700, Alex Williamson wrote:
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Why? Optimization?
hw/device-assignment.c | 17 +++--
hw/device-assignment.h |1 +
2 files changed, 8 insertions(+), 10 deletions(-)
diff
On Tue, Jan 31, 2012 at 08:16:31PM +0100, Jan Kiszka wrote:
On 2012-01-31 20:12, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 12:07:39PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:22:09AM -0700, Alex Williamson
On Tue, 2012-01-31 at 22:18 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:22:04AM -0700, Alex Williamson wrote:
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Why? Optimization?
Because in 6/9 we'd have to calculate it again for resetting the msix
table and in
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at this chance.
Signed-off-by: Jan Kiszkajan.kis...@siemens.com
Heh, I did this too more or less the same way. Some comments below:
---
On Tue, Jan 31, 2012 at 01:31:59PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 22:18 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:22:04AM -0700, Alex Williamson wrote:
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Why? Optimization?
Because
On Tue, 2012-01-31 at 22:19 +0200, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 08:16:31PM +0100, Jan Kiszka wrote:
On 2012-01-31 20:12, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 12:07:39PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin
On Tue, 2012-01-31 at 15:33 +0200, Avi Kivity wrote:
On 01/31/2012 03:21 PM, Jan Kiszka wrote:
On 2012-01-31 14:10, Avi Kivity wrote:
On 01/31/2012 02:57 PM, Jan Kiszka wrote:
Seems fine, but do we really need the option? If it doesn't work we
should treat it as an ordinary but and
On Tue, 2012-01-31 at 14:45 +0200, Avi Kivity wrote:
On 01/28/2012 04:21 PM, Alex Williamson wrote:
Stop using compatibility mode and at the same time fix available
access sizes. The PCI spec indicates that the MSI-X table may
only be accessed as DWORD or QWORD.
static const
On Tue, Jan 31, 2012 at 02:08:38PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 15:33 +0200, Avi Kivity wrote:
On 01/31/2012 03:21 PM, Jan Kiszka wrote:
On 2012-01-31 14:10, Avi Kivity wrote:
On 01/31/2012 02:57 PM, Jan Kiszka wrote:
Seems fine, but do we really need the
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output level and applies it when legacy
mode is turned off again. This value has to be preserved across save/
restore as it cannot be reconstructed
On Tue, 2012-01-31 at 22:00 +0200, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 12:05:49PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:21:58AM -0700, Alex Williamson wrote:
This makes access much easier.
On Tue, Jan 31, 2012 at 02:17:30PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 22:00 +0200, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 12:05:49PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200, Michael S. Tsirkin wrote:
On Sat, Jan 28, 2012 at 07:21:58AM
On Tue, 2012-01-31 at 23:24 +0200, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 02:17:30PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 22:00 +0200, Michael S. Tsirkin wrote:
On Tue, Jan 31, 2012 at 12:05:49PM -0700, Alex Williamson wrote:
On Tue, 2012-01-31 at 19:40 +0200,
On 01/31/2012 12:46 PM, Jan Kiszka wrote:
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming KVM in-kernel version. We share most of the
public interface of the i8254, specifically to
On 2012-01-31 22:40, Anthony Liguori wrote:
On 01/31/2012 12:46 PM, Jan Kiszka wrote:
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming KVM in-kernel version. We share most of the
On 01/31/2012 03:49 PM, Jan Kiszka wrote:
On 2012-01-31 22:40, Anthony Liguori wrote:
On 01/31/2012 12:46 PM, Jan Kiszka wrote:
Applying the concept used for the *PICs once again: establish a base
class for the i8254 that can be used both by the current user space
emulation and the upcoming
On 2012-01-31 21:49, Anthony Liguori wrote:
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
Convert the PC speaker device to a qdev ISA model. Move the public
interface to a dedicated header file at this chance.
Signed-off-by: Jan Kiszkajan.kis...@siemens.com
Heh, I did this too more or less the
On 2012-01-31 22:02, Anthony Liguori wrote:
On 01/31/2012 11:41 AM, Jan Kiszka wrote:
In legacy mode, the HPET suppresses the RTC interrupt delivery via IRQ
8 but keeps track of the RTC output level and applies it when legacy
mode is turned off again. This value has to be preserved across
1 - 100 of 140 matches
Mail list logo
