On Fri, Sep 06, 2013 at 09:38:21AM +1000, Alexey Kardashevskiy wrote:
On 09/06/2013 04:10 AM, Gleb Natapov wrote:
On Wed, Sep 04, 2013 at 02:01:28AM +1000, Alexey Kardashevskiy wrote:
On 09/03/2013 08:53 PM, Gleb Natapov wrote:
On Mon, Sep 02, 2013 at 01:14:29PM +1000, Alexey Kardashevskiy
On 09/06/2013 04:01 PM, Gleb Natapov wrote:
On Fri, Sep 06, 2013 at 09:38:21AM +1000, Alexey Kardashevskiy wrote:
On 09/06/2013 04:10 AM, Gleb Natapov wrote:
On Wed, Sep 04, 2013 at 02:01:28AM +1000, Alexey Kardashevskiy wrote:
On 09/03/2013 08:53 PM, Gleb Natapov wrote:
On Mon, Sep 02, 2013
On Fri, Sep 06, 2013 at 10:58:16AM +0530, Aneesh Kumar K.V wrote:
Paul Mackerras pau...@samba.org writes:
This enables us to use the Processor Compatibility Register (PCR) on
POWER7 to put the processor into architecture 2.05 compatibility mode
when running a guest. In this mode the new
On Thu, Sep 05, 2013 at 02:05:09PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-03 at 13:53 +0300, Gleb Natapov wrote:
Or supporting all IOMMU links (and leaving emulated stuff as is) in on
device is the last thing I have to do and then you'll ack the patch?
I am concerned
On 09/06/2013 04:57 PM, Gleb Natapov wrote:
On Thu, Sep 05, 2013 at 02:05:09PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-03 at 13:53 +0300, Gleb Natapov wrote:
Or supporting all IOMMU links (and leaving emulated stuff as is) in on
device is the last thing I have to do and then
On 5 September 2013 19:53, Grigory Makarevich
grigorymakarev...@gmail.com wrote:
Hi Maciej,
Any chance the physical time on source and target hosts differ too much, so
that after some migrations,
the delta goes over the range ?
All machines (including VM) are synchronized by ntpd from the
This allows the host kernel to handle H_PUT_TCE, H_PUT_TCE_INDIRECT
and H_STUFF_TCE requests targeted an IOMMU TCE table without passing
them to user space which saves time on switching to user space and back.
Both real and virtual modes are supported. The kernel tries to
handle a TCE request in
On 09/06/2013 04:57 PM, Gleb Natapov wrote:
On Thu, Sep 05, 2013 at 02:05:09PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-03 at 13:53 +0300, Gleb Natapov wrote:
Or supporting all IOMMU links (and leaving emulated stuff as is) in on
device is the last thing I have to do and then
Dear Friend,
I must say that I have enormous respect for you considering the manner in
which I have made contact with you. My name is Mr. Gordon Kumar, The
financial controller at the RESERVE BANK OF INDIA (Main Branch) in New
Delhi, INDIA, and I am getting in touch with you regarding a business
With the currently available struct kvm_s390_interrupt it is not possible to
inject every kind of interrupt as defined in the z/Architecture. Add
additional interruption parameters to the structures and move it to kvm.h
Signed-off-by: Jens Freimann jf...@linux.vnet.ibm.com
Reviewed-by: Cornelia
Add symbols required for the s390 floating interrupt controller (flic)
Signed-off-by: Jens Freimann jf...@linux.vnet.ibm.com
---
linux-headers/asm-s390/kvm.h | 5
linux-headers/linux/kvm.h| 65
2 files changed, 70 insertions(+)
diff --git
This patchset enables the s390 floating interrupt controller kvm_device.
It is used to
* clear all pending floating interrupts in the kernel at device reset
* inject/retrieve interrupts into the kernel (used for migration)
Please note that the linux-headers changes are not yet merged by
This patch adds a floating irq controller as a kvm_device.
It will be necessary for migration of floating interrupts as well
as for hardening the reset code by allowing user space to explicitly
remove all pending floating interrupts.
Signed-off-by: Jens Freimann jf...@linux.vnet.ibm.com
This series adds a kvm_device that acts as a irq controller for floating
interrupts. As a first step it implements functionality to retrieve and inject
interrupts for the purpose of migration and for hardening the reset code by
allowing user space to explicitly remove all pending floating
This patch implements a floating-interrupt controller device (flic)
which interacts with the s390 flic kvm_device.
It provides functionality to:
* clear all pending floating interrupts in the kernel at device reset
* inject/retrieve interrupts into the kernel (used for migration)
On 6 September 2013 13:19, Jens Freimann jf...@linux.vnet.ibm.com wrote:
Add symbols required for the s390 floating interrupt controller (flic)
Updates to linux-headers should be the result of a sync
against a specified mainline kernel revision, please
(otherwise this should be an RFC patchset).
On 6 September 2013 13:19, Jens Freimann jf...@linux.vnet.ibm.com wrote:
@@ -839,6 +903,7 @@ struct kvm_device_attr {
#define KVM_DEV_TYPE_FSL_MPIC_20 1
#define KVM_DEV_TYPE_FSL_MPIC_42 2
#define KVM_DEV_TYPE_XICS 3
+#define KVM_DEV_TYPE_FLIC 4
On 06/09/13 14:19, Jens Freimann wrote:
Add symbols required for the s390 floating interrupt controller (flic)
Signed-off-by: Jens Freimann jf...@linux.vnet.ibm.com
As Peter said, this should come via a sync, but you already mentioned that
in your cover-letter. I will Ack the kernel patch and
On 06/09/13 14:19, Jens Freimann wrote:
With the currently available struct kvm_s390_interrupt it is not possible to
inject every kind of interrupt as defined in the z/Architecture. Add
additional interruption parameters to the structures and move it to kvm.h
Signed-off-by: Jens Freimann
On 06/09/13 14:19, Jens Freimann wrote:
This patch adds a floating irq controller as a kvm_device.
It will be necessary for migration of floating interrupts as well
as for hardening the reset code by allowing user space to explicitly
remove all pending floating interrupts.
Signed-off-by:
On 06/09/13 14:19, Jens Freimann wrote:
This patch implements a floating-interrupt controller device (flic)
which interacts with the s390 flic kvm_device.
It provides functionality to:
* clear all pending floating interrupts in the kernel at device reset
* inject/retrieve interrupts
On 06/09/13 14:19, Jens Freimann wrote: This series adds a kvm_device that
acts as a irq controller for floating
interrupts. As a first step it implements functionality to retrieve and
inject
interrupts for the purpose of migration and for hardening the reset code by
allowing user space to
https://bugzilla.kernel.org/show_bug.cgi?id=60863
Bug ID: 60863
Summary: monitor usb_add host does not work correct
Product: Virtualization
Version: unspecified
Kernel Version: 3.10.10
Hardware: x86-64
OS: Linux
Hello. I have battery-backed RAID on my host machine. So I want to
choose appropriate caching mode for KVM. I use lvm volumes as raw
disks. So, I have composed table (while looking to sources):
---
NOCACHE CACHE_WBNO_FLUSH
Are there any optimizations that I can do for EOI/APIC for a Windows
2008R2 guest? I'm seeing a significant amount of kernel CPU usage from
kvm_ioapic_update_eoi. I can't seem to find any information on further
optimizations for this.
Sample of trace output:
On Fri, Sep 06, 2013 at 09:38:21AM +1000, Alexey Kardashevskiy wrote:
On 09/06/2013 04:10 AM, Gleb Natapov wrote:
On Wed, Sep 04, 2013 at 02:01:28AM +1000, Alexey Kardashevskiy wrote:
On 09/03/2013 08:53 PM, Gleb Natapov wrote:
On Mon, Sep 02, 2013 at 01:14:29PM +1000, Alexey Kardashevskiy
On 09/06/2013 04:01 PM, Gleb Natapov wrote:
On Fri, Sep 06, 2013 at 09:38:21AM +1000, Alexey Kardashevskiy wrote:
On 09/06/2013 04:10 AM, Gleb Natapov wrote:
On Wed, Sep 04, 2013 at 02:01:28AM +1000, Alexey Kardashevskiy wrote:
On 09/03/2013 08:53 PM, Gleb Natapov wrote:
On Mon, Sep 02, 2013
On Fri, Sep 06, 2013 at 10:58:16AM +0530, Aneesh Kumar K.V wrote:
Paul Mackerras pau...@samba.org writes:
This enables us to use the Processor Compatibility Register (PCR) on
POWER7 to put the processor into architecture 2.05 compatibility mode
when running a guest. In this mode the new
On Thu, Sep 05, 2013 at 02:05:09PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-03 at 13:53 +0300, Gleb Natapov wrote:
Or supporting all IOMMU links (and leaving emulated stuff as is) in on
device is the last thing I have to do and then you'll ack the patch?
I am concerned
On 09/06/2013 04:57 PM, Gleb Natapov wrote:
On Thu, Sep 05, 2013 at 02:05:09PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-03 at 13:53 +0300, Gleb Natapov wrote:
Or supporting all IOMMU links (and leaving emulated stuff as is) in on
device is the last thing I have to do and then
This allows the host kernel to handle H_PUT_TCE, H_PUT_TCE_INDIRECT
and H_STUFF_TCE requests targeted an IOMMU TCE table without passing
them to user space which saves time on switching to user space and back.
Both real and virtual modes are supported. The kernel tries to
handle a TCE request in
On 09/06/2013 04:57 PM, Gleb Natapov wrote:
On Thu, Sep 05, 2013 at 02:05:09PM +1000, Benjamin Herrenschmidt wrote:
On Tue, 2013-09-03 at 13:53 +0300, Gleb Natapov wrote:
Or supporting all IOMMU links (and leaving emulated stuff as is) in on
device is the last thing I have to do and then
I have a query about the ARM SMMU driver. In the ARM smmu driver I see, that
bus notifiers are registered for both amba and platform bus. Amba is the I/O
interconnect, right? Why is bus notifier required for the amba bus?
-Varun
-Original Message-
From: Yoder Stuart-B08248
Sent:
Adding Will...
-Original Message-
From: Sethi Varun-B16395
Sent: Friday, September 06, 2013 11:56 AM
To: Yoder Stuart-B08248; Wood Scott-B07421; Bhushan Bharat-R65777; 'Peter
Maydell'; 'Santosh Shukla'; 'Alex Williamson'; 'Alexander Graf';
'Antonios Motakis'; 'Christoffer Dall';
34 matches
Mail list logo
