Rusty Russell ru...@rustcorp.com.au writes:
Avi Kivity a...@redhat.com writes:
On 09/05/2012 10:58 AM, Rusty Russell wrote:
This is the generic part of the KVM_SET_ONE_REG/KVM_GET_ONE_REG
enhancements which ARM wants, rebased onto kvm/next.
This was stalled for so long it needs rebasing
On 10/18/2012 12:20 PM, Rusty Russell wrote:
Asias He as...@redhat.com writes:
+#define BLK_HDR 0
What's this for, exactly? Please add a comment.
The block headr is in the first and separate buffer.
Please don't assume this! We're trying to fix all the assumptions in
qemu at the
Hey all,
at the moment I am looking for hardware for a KVM host, but on a few
points I realy have problems to get a good hardware setup.
My situation is the following: I need a server with minimal energy
consumption, the ability of PCI Passtrough (so IOMMU is needed) and good
support for
To: kvm@vger.kernel.org
From: msch...@gmx.eu
Subject: Re: Shared IRQ with PCI Passthrough?
Date: Thu, 18 Oct 2012 20:09:56 +
Jan Kiszka jan.kiszka at siemens.com writes:
On 2012-10-15 11:07, Marco wrote:
Jan Kiszka jan.kiszka at
After commit b3356bf0dbb349 (KVM: emulator: optimize rep ins handling),
the pieces of io data can be collected and write them to the guest memory
or MMIO together.
Unfortunately, kvm splits the mmio access into 8 bytes and store them to
vcpu-mmio_fragments. If the guest uses rep ins to move large
Add the test to trigger the bug that rep ins causes vcpu-mmio_fragments
overflow overflow while move large data from ioport to MMIO
Signed-off-by: Xiao Guangrong xiaoguangr...@linux.vnet.ibm.com
---
x86/emulator.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff
On 10/18/2012 06:09 PM, Avi Kivity wrote:
On 10/09/2012 08:51 PM, Raghavendra K T wrote:
Here is the summary:
We do get good benefit by increasing ple window. Though we don't
see good benefit for kernbench and sysbench, for ebizzy, we get huge
improvement for 1x scenario. (almost 2/3rd of ple
On 10/15/2012 08:04 PM, Andrew Theurer wrote:
On Mon, 2012-10-15 at 17:40 +0530, Raghavendra K T wrote:
On 10/11/2012 01:06 AM, Andrew Theurer wrote:
On Wed, 2012-10-10 at 23:24 +0530, Raghavendra K T wrote:
On 10/10/2012 08:29 AM, Andrew Theurer wrote:
On Wed, 2012-10-10 at 00:21 +0530,
Am Donnerstag, 18. Oktober 2012, 18:05:39 schrieb Avi Kivity:
On 10/18/2012 05:50 PM, Guido Winkelmann wrote:
Am Mittwoch, 17. Oktober 2012, 13:25:45 schrieb Brian Jackson:
On Wednesday, October 17, 2012 10:45:14 AM Guido Winkelmann wrote:
vda1, logical block 1858771
Oct 17 17:12:04
On Fri, 2012-10-19 at 14:00 +0530, Raghavendra K T wrote:
On 10/15/2012 08:04 PM, Andrew Theurer wrote:
On Mon, 2012-10-15 at 17:40 +0530, Raghavendra K T wrote:
On 10/11/2012 01:06 AM, Andrew Theurer wrote:
On Wed, 2012-10-10 at 23:24 +0530, Raghavendra K T wrote:
On 10/10/2012 08:29 AM,
MySQl might not run good locally on the disk in the VM. It is actually
not a good idea to run it on nfs filesystem. The startup should not be a
problem. Once the data grows up, it will become the problem to you. Try
to cache as much as possible that would be helping you out from lots of
On Fri, Oct 19, 2012 at 2:19 AM, Rusty Russell ru...@rustcorp.com.au wrote:
Rusty Russell ru...@rustcorp.com.au writes:
Avi Kivity a...@redhat.com writes:
On 09/05/2012 10:58 AM, Rusty Russell wrote:
This is the generic part of the KVM_SET_ONE_REG/KVM_GET_ONE_REG
enhancements which ARM wants,
KVM_PV_REASON_PAGE_NOT_PRESENT kicks cpu out of idleness, but we haven't
marked that spot as an exit from idleness.
Not doing so can cause RCU warnings such as:
[ 732.788386] ===
[ 732.789803] [ INFO: suspicious RCU usage. ]
[ 732.790032] 3.7.0-rc1-next-20121019
On Thu, Oct 18, 2012 at 12:33 PM, Avi Kivity a...@redhat.com wrote:
On 10/18/2012 11:27 AM, Vasilis Liaskovitis wrote:
On Wed, Oct 17, 2012 at 12:03:51PM +0200, Avi Kivity wrote:
On 10/17/2012 11:19 AM, Vasilis Liaskovitis wrote:
I don't think so, but probably there's a limit of DIMMs that
On Thu, Oct 18, 2012 at 8:20 AM, Avi Kivity a...@redhat.com wrote:
On 10/14/2012 02:04 AM, Christoffer Dall wrote:
Used to initialize the in-kernel interrupt controller. On ARM we need to
map the virtual generic interrupt controller (vGIC) into Hyp the guest's
physicall address space so the
On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 14 October 2012 01:04, Christoffer Dall
c.d...@virtualopensystems.com wrote:
On ARM (and possibly other architectures) some bits are specific to the
model being emulated for the guest and user space needs a way
On 19 October 2012 19:46, Christoffer Dall
c.d...@virtualopensystems.com wrote:
On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
This doesn't say whether userspace is allowed to make this ioctl
multiple times for the same device. This could be any of:
*
On Fri, Oct 19, 2012 at 4:24 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 19 October 2012 19:46, Christoffer Dall
c.d...@virtualopensystems.com wrote:
On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
This doesn't say whether userspace is allowed to make
On Fri, Oct 19, 2012 at 4:27 PM, Christoffer Dall
c.d...@virtualopensystems.com wrote:
On Fri, Oct 19, 2012 at 4:24 PM, Peter Maydell peter.mayd...@linaro.org
wrote:
On 19 October 2012 19:46, Christoffer Dall
c.d...@virtualopensystems.com wrote:
On Wed, Oct 17, 2012 at 4:29 PM, Peter Maydell
] [ INFO: suspicious RCU usage. ]
[ 732.790032] 3.7.0-rc1-next-20121019-sasha-2-g6d8d02d-dirty #63
Tainted: GW
[ 732.790032] ---
[ 732.790032] include/linux/rcupdate.h:738 rcu_read_lock() used illegally
while idle!
[ 732.790032]
[ 732.790032] other info
On Thursday 18 October 2012, Avi Kivity wrote:
On 10/18/2012 11:35 AM, Gleb Natapov wrote:
You misunderstood the description. V_INTR_MASKING=1 means that
CR8 writes are not propagated to real HW APIC.
But KVM does not trap access to CR8 unconditionally. It enables
CR8 intercept only
I'm using libvirt 0.10.2 and I had qemu-kvm 1.1.1 running all my VMs.
I used libvirt's managedsave command to pause all the VMs and write
them to disk and when I brought up the machine again I had upgraded to
qemu-kvm 1.1.2 and attempted to resume the VMs from their state. It
unfortunately fails.
We need a way to specify the address at which we expect VMs to access
the interrupt controller (both the emulated distributor and the hardware
interface supporting virtualization). User space should decide on this
address as user space decides on an emulated board and loads a device
tree
On ARM (and possibly other architectures) some bits are specific to the
model being emulated for the guest and user space needs a way to tell
the kernel about those bits. An example is mmio device base addresses,
where KVM must know the base address for a given device to properly
emulate mmio
The vgic virtual cpu and emulated distributor interfaces must
be mapped at a given physical address in the guest. This address is
provided through the KVM_SET_DEVICE_ADDRESS ioctl, which happens after
the KVM_CREATE_IRQCHIP ioctl is called, but before the first VCPU is
excuted thorugh KVM_RUN.
25 matches
Mail list logo
