to play with this with only qemu (w/o libvirt).
>
> Thank you very much!
>
> Dongli Zhang
>
> On 01/08/2019 06:29 AM, Venu Busireddy wrote:
> > From: Sridhar Samudrala
> >
> > This feature bit can be used by a hypervisor to indicate to the virtio_net
>
From: Sridhar Samudrala
This feature bit can be used by a hypervisor to indicate to the virtio_net
device that it can act as a standby for another device with the same MAC
address.
Signed-off-by: Sridhar Samudrala
Signed-off-by: Venu Busireddy
---
hw/net/virtio-net.c | 2 ++
1 file changed
e vfio-pci devices. Only the vfio-pci devices that have this property
enabled are removed from the guest upon reboot.
Signed-off-by: Venu Busireddy
---
hw/acpi/pcihp.c | 27 +++
hw/net/virtio-net.c | 24
hw/vfio/pci.c| 3 +++
hw/
Add a query command to check the status of the FAILOVER_STANDBY_CHANGED
state of the virtio_net devices.
Signed-off-by: Venu Busireddy
---
hw/net/virtio-net.c| 16 +++
include/hw/virtio/virtio-net.h | 1 +
include/net/net.h | 2 ++
net/net.c
-by: Venu Busireddy
---
hw/vfio/pci.c | 57 +
qapi/net.json | 26 ++
2 files changed, 83 insertions(+)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index bd83b58..adcc95a 100644
--- a/hw/vfio/pci.c
+++ b/hw/vfio/pci.c
VIRTIO_NET_F_STANDBY feature bit.
Venu Busireddy (2):
virtio_net: Add support for "Data Path Switching" during Live Migration.
virtio_net: Add a query command for FAILOVER_STANDBY_CHANGED event.
---
Changes in v3:
Fix issues with coding style in patch 3/5.
Changes in v2:
Added a que
On 2018-12-10 12:31:43 -0500, Michael S. Tsirkin wrote:
> On Mon, Dec 10, 2018 at 11:15:48AM -0500, Venu Busireddy wrote:
> > From: Si-Wei Liu
> >
> > When a VF is hotplugged into the guest, datapath switching will be
> > performed immediately, which is sub
On 2018-12-10 13:28:42 -0600, Eric Blake wrote:
> On 12/10/18 10:15 AM, Venu Busireddy wrote:
> > Added two new events, FAILOVER_PLUG_PRIMARY and FAILOVER_UNPLUG_PRIMARY.
> > The first is emitted when the guest negotiates the F_STANDBY feature
> > bit. The second is emitte
-by: Venu Busireddy
---
hw/vfio/pci.c | 57 +
qapi/net.json | 26 ++
2 files changed, 83 insertions(+)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index bd83b58..adcc95a 100644
--- a/hw/vfio/pci.c
+++ b/hw/vfio/pci.c
From: Si-Wei Liu
Signed-off-by: Si-Wei Liu
Signed-off-by: Venu Busireddy
---
hmp.c | 5 +
hw/pci/pci.c | 5 +
qapi/misc.json | 5 -
3 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/hmp.c b/hmp.c
index 7828f93..7a75c93 100644
--- a/hmp.c
+++ b/hmp.c
Add a query command to check the status of the FAILOVER_STANDBY_CHANGED
state of the virtio_net devices.
Signed-off-by: Venu Busireddy
---
hw/net/virtio-net.c| 16
include/hw/virtio/virtio-net.h | 1 +
include/net/net.h | 2 ++
net/net.c
e vfio-pci devices. Only the vfio-pci devices that have this property
enabled are removed from the guest upon reboot.
Signed-off-by: Venu Busireddy
---
hw/acpi/pcihp.c | 27 +++
hw/net/virtio-net.c | 24
hw/vfio/pci.c| 3 +++
hw/
From: Sridhar Samudrala
This feature bit can be used by a hypervisor to indicate to the virtio_net
device that it can act as a standby for another device with the same MAC
address.
Signed-off-by: Sridhar Samudrala
Signed-off-by: Venu Busireddy
---
hw/net/virtio-net.c | 2 ++
1 file changed
VIRTIO_NET_F_STANDBY feature bit.
Venu Busireddy (2):
virtio_net: Add support for "Data Path Switching" during Live Migration.
virtio_net: Add a query command for FAILOVER_STANDBY_CHANGED event.
---
Changes in v2:
Added a query command for FAILOVER_STANDBY_CHANGED event.
Added a que
ci devices. Only the vfio-pci devices that have this property
enabled are removed from the guest upon reboot.
Signed-off-by: Venu Busireddy
---
hw/acpi/pcihp.c| 27 ++
hw/net/virtio-net.c| 23 ++
hw/vfio/pci.c |
-by: Venu Busireddy
---
hw/vfio/pci.c | 57 +
qapi/net.json | 26 ++
2 files changed, 83 insertions(+)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index ce1f33c..ea24ca2 100644
--- a/hw/vfio/pci.c
+++ b/hw/vfio/pci.c
From: Sridhar Samudrala
This feature bit can be used by a hypervisor to indicate to the virtio_net
device that it can act as a standby for another device with the same MAC
address.
Signed-off-by: Sridhar Samudrala
Signed-off-by: Venu Busireddy
---
hw/net/virtio-net.c | 2 ++
1 file changed
but just offers simplicity of implementation.
Sridhar Samudrala (1):
virtio_net: Add VIRTIO_NET_F_STANDBY feature bit.
Venu Busireddy (1):
virtio_net: Add support for "Data Path Switching" during Live Migration.
Si-Wei Liu (1):
vfio-pci: Add FAILOVER_PRIMARY_CHANGED event
On 2018-09-18 09:35:48 -0400, Michael S. Tsirkin wrote:
> On Tue, Sep 18, 2018 at 12:20:52PM +0200, Cornelia Huck wrote:
> > On Wed, 12 Sep 2018 11:22:12 -0400
> > "Michael S. Tsirkin" wrote:
> >
> > > On Wed, Sep 12, 2018 at 08:17:45AM -0700, Samudrala, Sridhar wrote:
> > > >
> > > >
> > > >
On 2018-07-07 15:14:11 +0300, Marcel Apfelbaum wrote:
> Hi Venu,
>
> On 06/30/2018 01:19 AM, Venu Busireddy wrote:
> > Add a new bridge device "pcie-downstream" with a
> > Vendor ID of PCI_VENDOR_ID_REDHAT and a Device ID of
> > PCI_DEVICE_ID_REDHAT
On 2018-07-10 05:11:18 +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 29, 2018 at 05:19:03PM -0500, Venu Busireddy wrote:
> > The current patch set includes all the feedback received for proposals [3]
> > and [4]. For the sake of completeness, patch for the virtio specificat
On 2018-07-03 12:58:25 +0300, Roman Kagan wrote:
> On Mon, Jul 02, 2018 at 02:14:52PM -0700, si-wei liu wrote:
> > On 7/2/2018 9:14 AM, Roman Kagan wrote:
> > > On Fri, Jun 29, 2018 at 05:19:03PM -0500, Venu Busireddy wrote:
> > > > The patch set "En
io device with the passthrough device attached to
that bridge.
This capability is added to the bridge iff the "failover-group-id"
option is specified for the bridge.
Signed-off-by: Venu Busireddy
---
default-configs/arm-softmmu.mak| 1 +
default-configs/i386-softmmu.mak | 1 +
VICE_ID_REDHAT_BRIDGE_FAILOVER
to avoid confusion with bridges that don't have this capability.
This capability is added to the bridge iff the "failover-group-id"
option is specified for the bridge.
Signed-off-by: Venu Busireddy
---
hw/pci-bridge/pci_bridge_dev.c | 10 +++
Add VIRTIO_PCI_CAP_GROUP_ID_CFG (Group Identifier) capability to the
virtio PCI capabilities to allow for the grouping of devices.
Signed-off-by: Venu Busireddy
---
content.tex | 30 ++
1 file changed, 30 insertions(+)
diff --git a/content.tex b/content.tex
index
ce
named "pcie-downstream" with Red Hat Vendor ID, and include the
group identifier in this device.
- Added a new patch to enhance the "pci-bridge" device to support
the group identifier (for the i440FX model).
Venu Busireddy (3):
Add "Group Identifier" supp
lover-group-id" option is specified.
Group Identifier is used to pair a virtio device with a passthrough
device.
Signed-off-by: Venu Busireddy
---
hw/virtio/virtio-pci.c | 15 +++
hw/virtio/virtio-pci.h | 3 ++-
include/hw/pci/pci.h
On 2018-06-27 22:27:33 -0500, Venu Busireddy wrote:
> On 2018-06-28 04:54:16 +0300, Michael S. Tsirkin wrote:
> > On Wed, Jun 27, 2018 at 05:34:17PM -0500, Venu Busireddy wrote:
> > > On 2018-06-27 23:12:12 +0300, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 27,
On 2018-06-28 05:14:50 +0300, Michael S. Tsirkin wrote:
> On Wed, Jun 27, 2018 at 06:07:59PM -0500, Venu Busireddy wrote:
> > On 2018-06-26 23:08:12 -0500, Venu Busireddy wrote:
> > > On 2018-06-27 07:02:36 +0300, Michael S. Tsirkin wrote:
> > > > On Tue, Jun 26,
On 2018-06-28 04:54:16 +0300, Michael S. Tsirkin wrote:
> On Wed, Jun 27, 2018 at 05:34:17PM -0500, Venu Busireddy wrote:
> > On 2018-06-27 23:12:12 +0300, Michael S. Tsirkin wrote:
> > > On Wed, Jun 27, 2018 at 02:59:01PM -0500, Venu Busireddy wrote:
> > > > On 2018
On 2018-06-26 23:08:12 -0500, Venu Busireddy wrote:
> On 2018-06-27 07:02:36 +0300, Michael S. Tsirkin wrote:
> > On Tue, Jun 26, 2018 at 10:49:33PM -0500, Venu Busireddy wrote:
> > > Add the "Vendor-Specific" capability to the Red Hat PCI bridge device
> > >
On 2018-06-27 23:12:12 +0300, Michael S. Tsirkin wrote:
> On Wed, Jun 27, 2018 at 02:59:01PM -0500, Venu Busireddy wrote:
> > On 2018-06-27 22:47:05 +0300, Michael S. Tsirkin wrote:
> > > On Wed, Jun 27, 2018 at 02:29:58PM -0500, Venu Busireddy wrote:
> > > > On 20
On 2018-06-27 22:47:05 +0300, Michael S. Tsirkin wrote:
> On Wed, Jun 27, 2018 at 02:29:58PM -0500, Venu Busireddy wrote:
> > On 2018-06-27 15:24:58 +0300, Roman Kagan wrote:
> > > On Tue, Jun 26, 2018 at 10:49:30PM -0500, Venu Busireddy wrote:
> > > > The patch
On 2018-06-27 15:24:58 +0300, Roman Kagan wrote:
> On Tue, Jun 26, 2018 at 10:49:30PM -0500, Venu Busireddy wrote:
> > The patch set "Enable virtio_net to act as a standby for a passthru
> > device" [1] deals with live migration of guests that use passthrough
> > dev
On 2018-06-27 07:06:42 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 26, 2018 at 10:49:30PM -0500, Venu Busireddy wrote:
> > The patch set "Enable virtio_net to act as a standby for a passthru
> > device" [1] deals with live migration of guests that use passthr
On 2018-06-27 07:02:36 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 26, 2018 at 10:49:33PM -0500, Venu Busireddy wrote:
> > Add the "Vendor-Specific" capability to the Red Hat PCI bridge device
> > "pci-bridge", to contain the "Group Identifier"
Add VIRTIO_PCI_CAP_GROUP_ID_CFG (Group Identifier) capability to the
virtio PCI capabilities to allow for the grouping of devices.
Signed-off-by: Venu Busireddy
---
content.tex | 36
1 file changed, 36 insertions(+)
diff --git a/content.tex b/content.tex
It may not always be desirable to have a random UUID stuffed into the
'_field' member. Add a new boolean option '_default' that will allow
the caller to specify if a random UUID needs be generated or not.
Also modified the instance where this macro is used.
Signed-off-by: Venu Busireddy
---
hw
- As Michael Tsirkin suggested, instead of tweaking the ioh3420
device with Red Hat vendor ID, create a new PCIe bridge device
named "pcie-downstream" with Red Hat Vendor ID, and include the
group identifier in this device.
- Added a new patch to enhance the "pci-bri
the "uuid" option is specified
for the bridge.
Signed-off-by: Venu Busireddy
---
hw/pci-bridge/pci_bridge_dev.c | 8
hw/pci/pci_bridge.c| 26 ++
include/hw/pci/pcie.h | 1 +
3 files changed, 35 insertions(+)
diff --git a/hw/pci
; option is specified.
Group Identifier is used to pair a virtio device with a passthrough
device.
Signed-off-by: Venu Busireddy
---
hw/virtio/virtio-pci.c | 15 +++
hw/virtio/virtio-pci.h | 3 ++-
include/hw/pci/pci.h
On 2018-06-21 18:21:55 -0700, Siwei Liu wrote:
> On Thu, Jun 21, 2018 at 7:59 AM, Cornelia Huck wrote:
> > On Wed, 20 Jun 2018 22:48:58 +0300
> > "Michael S. Tsirkin" wrote:
> >
> >> On Wed, Jun 20, 2018 at 06:06:19PM +0200, Cornelia Huck wrote:
> >> > In any case, I'm not sure anymore why we'd
On 2018-06-19 21:53:01 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 19, 2018 at 01:36:17PM -0500, Venu Busireddy wrote:
> > On 2018-06-19 21:21:23 +0300, Michael S. Tsirkin wrote:
> > > On Tue, Jun 19, 2018 at 01:14:06PM -0500, Venu Busireddy wrote:
> > > > On 2018
On 2018-06-19 21:12:17 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 19, 2018 at 12:54:06PM -0500, Venu Busireddy wrote:
> > On 2018-06-19 20:30:06 +0300, Michael S. Tsirkin wrote:
> > > On Tue, Jun 19, 2018 at 11:32:28AM -0500, Venu Busireddy wrote:
> > > > Add VIRT
On 2018-06-19 20:24:12 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 19, 2018 at 11:32:26AM -0500, Venu Busireddy wrote:
> > Add a "Vendor-Specific" capability to the PCIe bridge, to contain the
> > "Group Identifier" (UUID) that will be used to pair a vir
On 2018-06-19 20:30:06 +0300, Michael S. Tsirkin wrote:
> On Tue, Jun 19, 2018 at 11:32:28AM -0500, Venu Busireddy wrote:
> > Add VIRTIO_PCI_CAP_GROUP_ID_CFG (Group Identifier) capability to the
> > virtio PCI capabilities to allow for the grouping of devices.
> >
&g
; option is specified.
Group Identifier is used to pair a virtio device with a passthrough
device.
Signed-off-by: Venu Busireddy
---
hw/virtio/virtio-pci.c | 15 +++
hw/virtio/virtio-pci.h | 3 ++-
include/standard-headers/linux/virtio_
Add VIRTIO_PCI_CAP_GROUP_ID_CFG (Group Identifier) capability to the
virtio PCI capabilities to allow for the grouping of devices.
Signed-off-by: Venu Busireddy
---
content.tex | 43 +++
1 file changed, 43 insertions(+)
diff --git a/content.tex b
It may not always be desirable to have a random UUID stuffed into the
'_field' member. Add a new option '_default' to the macro, that will
allow the caller to specify if a random UUID needs be generated or not.
Also modified the instance where this macro is used.
Signed-off-by: Venu Busireddy
tio device's
configuration space instead of the MAC address for pairing the devices.
Thanks!
Venu
[1] https://lists.oasis-open.org/archives/virtio-dev/201805/msg00156.html
[2] https://www.spinics.net/lists/netdev/msg499011.html
[3] https://lists.oasis-open.org/archives/virtio-dev/201805/ms
On 2018-06-04 20:42:45 +0300, Michael S. Tsirkin wrote:
> On Mon, Jun 04, 2018 at 11:44:40AM -0500, Venu Busireddy wrote:
> > On 2018-06-02 00:10:31 +0300, Michael S. Tsirkin wrote:
> > > On Sat, Jun 02, 2018 at 12:09:35AM +0300, Michael S. Tsirkin wrote:
> > > > On F
On 2018-06-01 23:03:16 +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 01, 2018 at 12:01:26PM -0500, Venu Busireddy wrote:
> > On 2018-06-01 18:42:06 +0300, Michael S. Tsirkin wrote:
> > > On Wed, May 23, 2018 at 11:16:12AM -0400, Venu Busireddy wrote:
> > > > D
On 2018-06-01 18:42:06 +0300, Michael S. Tsirkin wrote:
> On Wed, May 23, 2018 at 11:16:12AM -0400, Venu Busireddy wrote:
> > During live migration involving passthrough devices, the guest needs
> > to know which virtio device will be a fail-over device for a given
> &g
I looked at the discussion in the threads [1] and [2], where it was
suggested placing the passthrough device behind one bridge, and the virtio
device behind another bridge, and storing in those bridges' configuration
space some unique identifier that can be used to pair the two devices.
After
Add VIRTIO_PCI_CAP_GROUP_ID_CFG (Group Identifier) capability to the
virtio PCI capabilities to allow for the grouping of devices.
Signed-off-by: Venu Busireddy <venu.busire...@oracle.com>
---
content.tex | 43 +++
1 file changed, 43 insertions(+)
On 2018-05-22 11:03:37 +0100, Stefan Hajnoczi wrote:
> On Fri, May 18, 2018 at 04:43:36PM -0500, Venu Busireddy wrote:
> > On 2018-05-18 17:06:23 +0100, Stefan Hajnoczi wrote:
> > > On Thu, May 17, 2018 at 09:06:04AM -0400, Venu Busireddy wrote:
> > >
> > &g
On 2018-05-18 17:06:23 +0100, Stefan Hajnoczi wrote:
> On Thu, May 17, 2018 at 09:06:04AM -0400, Venu Busireddy wrote:
>
> Can you describe a use case where vendor-specific extensions make sense
> as opposed to extending the VIRTIO specification?
Sometimes, qemu may need to group cer
rom 12h through 0FFh, it also provides a
"Vendor Specific" capability ID (0x09), to allow the device vendors to
use the capability mechanism for vendor specific information.
There are alternative ways to achieve the same objective, but the
implementation is much cleaner with a new virtio PCI c
Add VIRTIO_PCI_CAP_VENDOR_EXT_CFG to the virtio PCI capabilities to
allow vendors to define vendor specific extension.
Signed-off-by: Venu Busireddy <venu.busire...@oracle.com>
---
content.tex | 43 +++
1 file changed, 43 insertions(+)
diff
59 matches
Mail list logo
