From: "Michael S. Tsirkin" <mst@redhat.com>
To: Srujana Challa <schalla@marvell.com>
Cc: "virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"xuanzhuo@linux.alibaba.com" <xuanzhuo@linux.alibaba.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH v6] virtio: vdpa: vDPA driver for Marvell OCTEON DPU devices
Date: Thu, 11 Jul 2024 10:37:10 -0400 [thread overview]
Message-ID: <20240711103627-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DS0PR18MB5368CDFF8C115C8125C0287DA0A52@DS0PR18MB5368.namprd18.prod.outlook.com>
On Thu, Jul 11, 2024 at 01:01:37PM +0000, Srujana Challa wrote:
> > Subject: [PATCH v6] virtio: vdpa: vDPA driver for Marvell OCTEON DPU devices
> >
> > This commit introduces a new vDPA driver specifically designed for managing
> > the virtio control plane over the vDPA bus for OCTEON DPU devices. The driver
> > consists of two layers:
> >
> > 1. Octep HW Layer (Octeon Endpoint): Responsible for handling hardware
> > operations and configurations related to the DPU device.
> >
> > 2. Octep Main Layer: Compliant with the vDPA bus framework, this layer
> > implements device operations for the vDPA bus. It handles device probing, bus
> > attachment, vring operations, and other relevant tasks.
>
> Michael, could you kindly inform us if any additional actions are required from our end?
> Thanks.
As far as I know, you should see this driver in linux-next already.
Please check, if anything is missing, pls let me know.
--
MST
prev parent reply other threads:[~2024-07-11 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 14:46 [PATCH v6] virtio: vdpa: vDPA driver for Marvell OCTEON DPU devices Srujana Challa
2024-06-25 5:46 ` Srujana Challa
2024-07-11 13:01 ` Srujana Challa
2024-07-11 14:37 ` Michael S. Tsirkin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240711103627-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jerinj@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=schalla@marvell.com \
--cc=sthotton@marvell.com \
--cc=vattunuru@marvell.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.