On 20/02/14 20:24, Luis R. Rodriguez wrote:
On Thu, Feb 20, 2014 at 9:19 AM, Stephen Hemminger
step...@networkplumber.org wrote:
On Wed, 19 Feb 2014 09:59:33 -0800 Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Wed, Feb 19, 2014 at 9:08 AM, Stephen Hemminger step...@networkplumber.org
On 20/02/14 20:39, Luis R. Rodriguez wrote:
On Wed, Feb 19, 2014 at 11:13 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
On 19/02/14 17:20, Luis R. Rodriguez wrote:
On 19/02/14 17:20, Luis R. Rodriguez also wrote:
Zoltan has noted though some use cases of IPv4 or IPv6 addresses on
backends
On 20/02/14 20:01, Luis R. Rodriguez wrote:
On Thu, Feb 20, 2014 at 5:19 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
How about this: netback sets the root_block flag and a random MAC by
default. So the default behaviour won't change, DAD will be happy, and
userspace don't have to do anything
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel which is calling it to
retrieve the TCE set up by the panicing kernel.
On 21.02.2014, at 16:31, Laurent Dufour lduf...@linux.vnet.ibm.com wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel
On Fri, Feb 21, 2014 at 5:02 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
On 20/02/14 20:01, Luis R. Rodriguez wrote:
On Thu, Feb 20, 2014 at 5:19 AM, Zoltan Kiss zoltan.k...@citrix.com
wrote:
How about this: netback sets the root_block flag and a random MAC by
default. So the default
On Fri, Feb 21, 2014 at 5:02 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
Agreed that's the best strategy and I'll work on sending patches to
brctl to enable the root_block preference. This approach however also
I don't think brctl should deal with any Xen specific stuff. I assume there
is a
Hi Paolo et al,
Based on recently accepted to the mainline pci_enable_msix_exact() function,
I am sending a updated version of the patch. Please, let me know if it does
not work for you and you need and incremental update from the previous version.
Thanks!
--
Regards,
Alexander Gordeev
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Il 21/02/2014 18:05, Alexander Gordeev ha scritto:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and
From 24ffdce9efebf13c6ed4882f714b2b57ef1141eb Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Thu, 20 Feb 2014 17:38:26 +0800
Subject: [PATCH] KVM: x86: expose new instruction RDSEED to guest
RDSEED instruction return a random number, which supplied by a
cryptographically
Il 16/01/2014 13:44, Christian Borntraeger ha scritto:
+DEFINE_STATIC_SRCU(irq_srcu);
+
bool kvm_irq_has_notifier(struct kvm *kvm, unsigned irqchip, unsigned pin)
{
struct kvm_irq_ack_notifier *kian;
- int gsi;
+ int gsi, idx;
- rcu_read_lock();
- gsi =
From 0750e335eb5860b0b483e217e8a08bd743cbba16 Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Thu, 20 Feb 2014 17:39:32 +0800
Subject: [PATCH] KVM: x86: expose ADX feature to guest
ADCX and ADOX instructions perform an unsigned addition with Carry flag and
Overflow flag
From 00c920c96127d20d4c3bb790082700ae375c39a0 Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Fri, 21 Feb 2014 23:47:18 +0800
Subject: [PATCH] KVM: x86: Fix xsave cpuid exposing bug
EBX of cpuid(0xD, 0) is dynamic per XCR0 features enable/disable.
Bit 63 of XCR0 is reserved
These patches are version 4 to enable Intel MPX for KVM.
Version 1:
* Add some Intel MPX definiation
* Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0 features enable/disable
* vmx and msr handle for MPX support at KVM
* enalbe MPX feature for guest
Version 2:
* remove generic MPX
From eb56f19c14d5603209b22b97cd53ef1716bf2804 Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Sat, 22 Feb 2014 07:53:32 +0800
Subject: [PATCH v4 1/3] KVM: x86: Intel MPX vmx and msr handle
This patch handle vmx and msr of Intel MPX feature.
Signed-off-by: Xudong Hao
From 7d1b41c3fdf71e4c73280e117948102f54f74be7 Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Sat, 22 Feb 2014 08:10:17 +0800
Subject: [PATCH v4 2/3] KVM: x86: add MSR_IA32_BNDCFGS to msrs_to_save
Add MSR_IA32_BNDCFGS to msrs_to_save, and corresponding logic
to
From 8b3a3b1f08c166e0c2cdc6162e6fa95d9c7ad2ec Mon Sep 17 00:00:00 2001
From: Liu Jinsong jinsong@intel.com
Date: Sat, 22 Feb 2014 08:53:27 +0800
Subject: [PATCH v4 3/3] KVM: x86: Enable Intel MPX for guest
This patch enable Intel MPX feature to guest.
Signed-off-by: Xudong Hao
Paolo Bonzini wrote:
Il 22/01/2014 13:03, Paolo Bonzini ha scritto:
Il 22/01/2014 06:29, Liu, Jinsong ha scritto:
These patches are version 3 to enalbe Intel MPX for KVM.
Version 1:
* Add some Intel MPX definiation
* Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0 features
Il 21/02/2014 18:57, Liu, Jinsong ha scritto:
- F(BMI2) | F(ERMS) | f_invpcid | F(RTM) | F(RDSEED) |
+ F(BMI2) | F(ERMS) | f_invpcid | F(RTM) | F(MPX) | F(RDSEED) |
F(ADX);
MPX also needs to be conditional on mpx_supported here, like it is done
with
On Fri, Feb 21, 2014 at 06:11:29PM +0100, Paolo Bonzini wrote:
It's okay, but it's not clear to me whether I should include this
patch or someone else will. :)
Please, include it.
Thanks!
Paolo
--
Regards,
Alexander Gordeev
agord...@redhat.com
--
To unsubscribe from this list: send the
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel which is calling it
Il 21/02/2014 19:56, Alexander Gordeev ha scritto:
On Fri, Feb 21, 2014 at 06:11:29PM +0100, Paolo Bonzini wrote:
It's okay, but it's not clear to me whether I should include this
patch or someone else will. :)
Please, include it.
And where do I get pci_enable_msix_exact? When will
I plan to setup a headless KVM hypervisor (i.e. pci-stub assigned to
GPU) and guest Windows 7 with vga passthrough to AMD GPU as the only
screen (i.e. -vga none -device vfio-pci,*). I have SuperMicro
motherboard and a pair of Xeons E5-26*V2 and plenty of RAM for this, and
am not afraid of
On 02/22/2014 06:23 AM, Benjamin Herrenschmidt wrote:
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE
On 02/22/2014 11:28 AM, Alexey Kardashevskiy wrote:
On 02/22/2014 06:23 AM, Benjamin Herrenschmidt wrote:
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture
On Fri, Feb 21, 2014 at 8:01 AM, Luis R. Rodriguez
mcg...@do-not-panic.com wrote:
On Fri, Feb 21, 2014 at 5:02 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
Agreed that's the best strategy and I'll work on sending patches to
brctl to enable the root_block preference. This approach however also
On Fri, Feb 21, 2014 at 5:02 AM, Zoltan Kiss zoltan.k...@citrix.com wrote:
Check this how current Xen scripts does routed networking:
http://wiki.xen.org/wiki/Xen_Networking#Associating_routes_with_virtual_devices
Note, there are no bridges involved here! As the above page says, the
backend
On 21.02.2014, at 16:31, Laurent Dufour lduf...@linux.vnet.ibm.com wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE is required by the kdump kernel which is calling it
On 02/22/2014 06:23 AM, Benjamin Herrenschmidt wrote:
On Fri, 2014-02-21 at 16:31 +0100, Laurent Dufour wrote:
This fix introduces the H_GET_TCE hypervisor call which is basically the
reverse of H_PUT_TCE, as defined in the Power Architecture Platform
Requirements (PAPR).
The hcall H_GET_TCE
31 matches
Mail list logo
