Hi,
Well, we also want to clean up the registers, so how about:
BAR0: legacy, as is. If you access this, don't use the others.
Ok.
BAR1: new format virtio-pci layout. If you use this, don't use BAR0.
BAR2: virtio-cfg. If you use this, don't use BAR0.
Why use two bars for this? You
Il 09/10/2012 06:59, Rusty Russell ha scritto:
Paolo Bonzini pbonz...@redhat.com writes:
Il 05/10/2012 07:43, Rusty Russell ha scritto:
That's good. But virtio_blk's scsi command is insoluble AFAICT. As I
said to Anthony, the best rules are always and never, so I'd really
rather not have to
vhost-blk is an in-kernel virito-blk device accelerator.
Due to lack of proper in-kernel AIO interface, this version converts
guest's I/O request to bio and use submit_bio() to submit I/O directly.
So this version any supports raw block device as guest's disk image,
e.g. /dev/sda, /dev/ram0. We
Hi
Please send in any agenda topics that you have.
Thanks, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 10/09/2012 05:16 AM, Rusty Russell wrote:
Anthony Liguori aligu...@us.ibm.com writes:
We'll never remove legacy so we shouldn't plan on it. There are
literally hundreds of thousands of VMs out there with the current virtio
drivers installed in them. We'll be supporting them for a very,
On 10/08/2012 07:30 PM, Marcelo Tosatti wrote:
From Intel's manual:
• If an execution of WRMSR to the IA32_TIME_STAMP_COUNTER MSR adds (or
subtracts) value X from the TSC,
the logical processor also adds (or subtracts) value X from the
IA32_TSC_ADJUST MSR.
This is not handled in the
On 10/04/2012 02:14 PM, Peter Lieven wrote:
Hi,
kvm-kmod 3.6 fails to compile against a 3.2.0 kernel with the following error:
/usr/src/kvm-kmod-3.6/x86/x86.c: In function ‘get_msr_mce’:
/usr/src/kvm-kmod-3.6/x86/x86.c:1908:27: error: ‘kvm’ undeclared (first use
in this function)
On Sat, 6 Oct 2012 17:33:43 -0400, Christoffer Dall
c.d...@virtualopensystems.com wrote:
On Thu, Oct 4, 2012 at 10:23 PM, Min-gyu Kim mingyu84@samsung.com
wrote:
-Original Message-
From: kvm-ow...@vger.kernel.org [mailto:kvm-ow...@vger.kernel.org] On
Behalf Of Christoffer Dall
Juan Quintela quint...@redhat.com wrote:
Hi
Please send in any agenda topics that you have.
Hi
As there is no agenda, call gets cancelled.
Sorry for sending the request for agenda late.
Later, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
Rusty Russell ru...@rustcorp.com.au writes:
Anthony Liguori aligu...@us.ibm.com writes:
We'll never remove legacy so we shouldn't plan on it. There are
literally hundreds of thousands of VMs out there with the current virtio
drivers installed in them. We'll be supporting them for a very,
On Thu, 27 Sep 2012 09:59:33 +0930
Rusty Russell ru...@rustcorp.com.au wrote:
Hi all,
I've had several requests for a more formal approach to the
virtio draft spec, and (after some soul-searching) I'd like to try that.
The proposal is to use OASIS as the standards body, as
This makes QEMU recognize the following CPU flag names:
Flags| Corresponding KVM kernel commit
-+
FSGSBASE | 176f61da82435eae09cc96f70b530d1ba0746b8b
AVX2, BMI1, BMI2 | fb215366b3c7320ac25dca766a0152df16534932
HLE,
Avi Kivity a...@redhat.com writes:
On 10/09/2012 05:16 AM, Rusty Russell wrote:
Anthony Liguori aligu...@us.ibm.com writes:
We'll never remove legacy so we shouldn't plan on it. There are
literally hundreds of thousands of VMs out there with the current virtio
drivers installed in them.
On Tue, Oct 09, 2012 at 02:12:18PM +0200, Avi Kivity wrote:
On 10/08/2012 07:30 PM, Marcelo Tosatti wrote:
From Intel's manual:
• If an execution of WRMSR to the IA32_TIME_STAMP_COUNTER MSR adds (or
subtracts) value X from the TSC,
the logical processor also adds (or subtracts)
On 10/09/2012 04:24 PM, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:12:18PM +0200, Avi Kivity wrote:
On 10/08/2012 07:30 PM, Marcelo Tosatti wrote:
From Intel's manual:
• If an execution of WRMSR to the IA32_TIME_STAMP_COUNTER MSR adds (or
subtracts) value X from the TSC,
the
On Tue, Oct 09, 2012 at 04:26:32PM +0200, Avi Kivity wrote:
On 10/09/2012 04:24 PM, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:12:18PM +0200, Avi Kivity wrote:
On 10/08/2012 07:30 PM, Marcelo Tosatti wrote:
From Intel's manual:
• If an execution of WRMSR to the
On 10/09/2012 04:27 PM, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 04:26:32PM +0200, Avi Kivity wrote:
On 10/09/2012 04:24 PM, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:12:18PM +0200, Avi Kivity wrote:
On 10/08/2012 07:30 PM, Marcelo Tosatti wrote:
From Intel's manual:
On Wed, 19 Sep 2012 18:38:38 +0200
Alexander Graf ag...@suse.de wrote:
On 04.09.2012, at 17:13, Cornelia Huck wrote:
+static u32 virtio_ccw_get_features(struct virtio_device *vdev)
+{
+ struct virtio_ccw_device *vcdev = to_vc_device(vdev);
+ struct virtio_feature_desc features;
On Thu, 20 Sep 2012 09:27:00 -0500
Anthony Liguori aligu...@us.ibm.com wrote:
Cornelia Huck cornelia.h...@de.ibm.com writes:
This patch enables using both virtio-xxx-s390 and virtio-xxx-ccw
by making the alias lookup code verify that a driver is actually
registered.
(Only included in
Il 09/10/2012 16:36, Grzegorz Dwornicki ha scritto:
I have a question to you guys. Is it possible to use code from live
migration of KVM VMs to migrate other process?
No, because this is hardware migration. It migrates the whole machine
including the hardware state (e.g. the video card, or
On Tue, Oct 9, 2012 at 9:36 AM, Grzegorz Dwornicki gd1...@gmail.com wrote:
I have a question to you guys. Is it possible to use code from live
migration of KVM VMs to migrate other process?
As far as I can tell, no.
most of the virtualization facililites of KVM are implemented in the
kernel,
Gerd Hoffmann kra...@redhat.com writes:
Hi,
Well, we also want to clean up the registers, so how about:
BAR0: legacy, as is. If you access this, don't use the others.
Ok.
BAR1: new format virtio-pci layout. If you use this, don't use BAR0.
BAR2: virtio-cfg. If you use this, don't
I am just testing the second version of this patch. It addresses all the
comments so far except Marcelo's issue with breaking the function
compute_guest_tsc().
I needed to put the call for updating the TSC_ADJUST_MSR in kvm_write_tsc() to
ensure it is only called from user space. Other
On Tue, Oct 09, 2012 at 04:30:28PM +0200, Avi Kivity wrote:
On 10/09/2012 04:27 PM, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 04:26:32PM +0200, Avi Kivity wrote:
On 10/09/2012 04:24 PM, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:12:18PM +0200, Avi Kivity wrote:
On 10/08/2012
On Mon, Sep 24, 2012 at 10:32:05AM -0400, Don Slutz wrote:
These are modeled after x86_cpuid_get_xlevel and x86_cpuid_set_xlevel.
Signed-off-by: Don Slutz d...@cloudswitch.com
---
target-i386/cpu.c | 29 +
1 files changed, 29 insertions(+), 0 deletions(-)
On Mon, Sep 24, 2012 at 10:32:06AM -0400, Don Slutz wrote:
This is used to set the cpu object's hypervisor level to the default for
Microsoft's Hypervisor.
Signed-off-by: Don Slutz d...@cloudswitch.com
---
target-i386/cpu.c |9 +
target-i386/cpu.h |2 ++
2 files changed,
On 10/09/12 10:03, Eduardo Habkost wrote:
This makes QEMU recognize the following CPU flag names:
Flags| Corresponding KVM kernel commit
-+
FSGSBASE | 176f61da82435eae09cc96f70b530d1ba0746b8b
AVX2, BMI1, BMI2 |
Hi,
sorry for the delayed answer.
On Sat, Sep 29, 2012 at 11:13:04AM +, Blue Swirl wrote:
The -dimm option is supposed to specify the dimm/memory layout, and not
create
any devices.
If we don't want this new option, I have a question:
A -device/device_add means we create a
On Tue, Oct 09, 2012 at 01:34:09PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:06AM -0400, Don Slutz wrote:
This is used to set the cpu object's hypervisor level to the default for
Microsoft's Hypervisor.
Signed-off-by: Don Slutz d...@cloudswitch.com
---
On Mon, Sep 24, 2012 at 10:32:07AM -0400, Don Slutz wrote:
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
+static int vhost_blk_req_submit(struct vhost_blk_req *req, struct file *file)
+{
+
+ struct inode *inode = file-f_mapping-host;
+ struct block_device *bdev = inode-i_bdev;
+ int ret;
Please just pass the block_device directly instead of a file struct.
+
+ ret =
Hello Marcelo,
Here's a couple of backports for your stable-0.15 branch.
Except for one (marked as backported) these were all clean cherry-picks.
My proposal is to merge these KVM-only patches before qemu-stable-0.15.git,
where I will be tagging v0.15.2 shortly.
Cc: Marcelo Tosatti
From: Lai Jiangshan la...@cn.fujitsu.com
Currently, NMI interrupt is blindly sent to all the vCPUs when NMI
button event happens. This doesn't properly emulate real hardware on
which NMI button event triggers LINT1. Because of this, NMI is sent to
the processor even when LINT1 is maskied in LVT.
From: Alex Williamson alex.william...@redhat.com
Coverity found that we're doing (uint16_t)type 0xf0 8.
This is obviously always 0x0, so our attempt to filter out
some device types thinks everything is an endpoint. Fix
shift amount.
Signed-off-by: Alex Williamson alex.william...@redhat.com
From: Alex Williamson alex.william...@redhat.com
Another Coverity found issue, lnkcap is a 32bit register and
we're masking bits 16 17. Fix to uin32_t.
Signed-off-by: Alex Williamson alex.william...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
(cherry picked from commit
From: Jan Kiszka jan.kis...@siemens.com
Don't mess with assign_intx on devices that are in MSI or MSI-X mode, it
would corrupt their interrupt routing.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
(cherry picked from commit
From: Alex Williamson alex.william...@redhat.com
Markus Armbruster points out that we're missing a 0 check
from pread while trying to probe for pci-sysfs io-port
resource support. We don't expect a short read, but we
should harden the test to abort if we get one so we're not
potentially looking
From: Alex Williamson alex.william...@redhat.com
All the fields of lnkcap are read-only and this is setting it
with mask values from LNKCTL. Just below it, we indicate
link control is read only, so this appears to be a stray
chunk left in from development. Trivial comment fix while
we're here.
On 1 October 2012 10:11, Christoffer Dall c.d...@virtualopensystems.com wrote:
From: Rusty Russell rusty.russ...@linaro.org
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documentation/virtual/kvm/api.txt
@@ -1765,6 +1765,12 @@ ARM 64-bit CP15 registers have the following id bit
patterns:
On Tue, Oct 9, 2012 at 2:11 PM, Peter Maydell peter.mayd...@linaro.org wrote:
On 1 October 2012 10:11, Christoffer Dall c.d...@virtualopensystems.com
wrote:
From: Rusty Russell rusty.russ...@linaro.org
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documentation/virtual/kvm/api.txt
@@
On Tue, Oct 09, 2012 at 02:18:05PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:07AM -0400, Don Slutz wrote:
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
On Tue, Oct 09, 2012 at 03:27:26PM -0300, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:18:05PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:07AM -0400, Don Slutz wrote:
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor
* Avi Kivity a...@redhat.com [2012-10-04 17:00:28]:
On 10/04/2012 03:07 PM, Peter Zijlstra wrote:
On Thu, 2012-10-04 at 14:41 +0200, Avi Kivity wrote:
Again the numbers are ridiculously high for arch_local_irq_restore.
Maybe there's a bad perf/kvm interaction when we're injecting an
On 10/09/12 14:47, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 03:27:26PM -0300, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:18:05PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:07AM -0400, Don Slutz wrote:
Also known as Paravirtualization level.
This change is based
On Mon, Sep 24, 2012 at 10:32:10AM -0400, Don Slutz wrote:
These are modeled after x86_cpuid_set_vendor and x86_cpuid_get_vendor.
Since kvm's vendor is shorter, the test for correct size is removed and zero
padding is added.
Set Microsoft's Vendor now that we can. Value defined in:
On Mon, Sep 24, 2012 at 10:32:08AM -0400, Don Slutz wrote:
Also known as Paravirtualization level.
This change is based on:
Microsoft Hypervisor CPUID Leaves:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542428%28v=vs.85%29.aspx
Linux kernel change starts with:
On Mon, Sep 24, 2012 at 10:32:16AM -0400, Don Slutz wrote:
This was taken from:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/22643
Signed-off-by: Don Slutz d...@cloudswitch.com
---
target-i386/cpu.c | 32
1 files changed, 32 insertions(+), 0
On Tue, Oct 09, 2012 at 03:09:17PM -0400, Don Slutz wrote:
On 10/09/12 14:47, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 03:27:26PM -0300, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 02:18:05PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:07AM -0400, Don Slutz wrote:
On 10/09/12 13:17, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 01:34:09PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:06AM -0400, Don Slutz wrote:
This is used to set the cpu object's hypervisor level to the default for
Microsoft's Hypervisor.
Signed-off-by: Don Slutz
On 10/09/12 12:25, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:05AM -0400, Don Slutz wrote:
These are modeled after x86_cpuid_get_xlevel and x86_cpuid_set_xlevel.
Signed-off-by: Don Slutz d...@cloudswitch.com
---
target-i386/cpu.c | 29 +
1 files
On Tue, Oct 09, 2012 at 03:12:00PM -0400, Don Slutz wrote:
On 10/09/12 13:17, Marcelo Tosatti wrote:
On Tue, Oct 09, 2012 at 01:34:09PM -0300, Marcelo Tosatti wrote:
On Mon, Sep 24, 2012 at 10:32:06AM -0400, Don Slutz wrote:
This is used to set the cpu object's hypervisor level to the default
Hi,
Why use two bars for this? You can put them into one mmio bar, together
with the msi-x vector table and PBA. Of course a pci capability
describing the location is helpful for that ;)
You don't need a capability. You can also just add a config offset
field to the register set and
Rusty Russell wrote:
I don't think it'll be that bad; reset clears the device to unknown,
bar0 moves it from unknown-legacy mode, bar1/2/3 changes it from
unknown-modern mode, and anything else is bad (I prefer being strict so
we catch bad implementations from the beginning).
Will that work,
-Original Message-
From: Marc Zyngier [mailto:marc.zyng...@arm.com]
Sent: Tuesday, October 09, 2012 9:56 PM
To: Christoffer Dall
Cc: Min-gyu Kim; 김창환; linux-arm-ker...@lists.infradead.org;
kvm@vger.kernel.org; kvm...@lists.cs.columbia.edu
Subject: Re: [kvmarm] [PATCH v2 06/14]
Hello Christoph!
On 10/10/2012 01:39 AM, Christoph Hellwig wrote:
+static int vhost_blk_req_submit(struct vhost_blk_req *req, struct file
*file)
+{
+
+struct inode *inode = file-f_mapping-host;
+struct block_device *bdev = inode-i_bdev;
+int ret;
Please just pass the
On Wed, 2012-10-10 at 00:21 +0530, Raghavendra K T wrote:
* Avi Kivity a...@redhat.com [2012-10-04 17:00:28]:
On 10/04/2012 03:07 PM, Peter Zijlstra wrote:
On Thu, 2012-10-04 at 14:41 +0200, Avi Kivity wrote:
Again the numbers are ridiculously high for arch_local_irq_restore.
56 matches
Mail list logo
