DPDK patches and discussions
 help / color / mirror / Atom feed
From: Long Li <longli@microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"longli@linuxonhyperv.com" <longli@linuxonhyperv.com>
Cc: Wei Hu <weh@microsoft.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] Re: [patch v4 6/6] bus/vmbus: set event for channel without monitoring support
Date: Tue, 8 Apr 2025 21:55:12 +0000	[thread overview]
Message-ID: <SA6PR21MB4231ED0D3C3B0D1684CCE0DACEB52@SA6PR21MB4231.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20250408071813.680880e7@hermes.local>

> Subject: [EXTERNAL] Re: [patch v4 6/6] bus/vmbus: set event for channel without
> monitoring support
> 
> On Mon,  7 Apr 2025 15:45:04 -0700
> longli@linuxonhyperv.com wrote:
> 
> > From: Long Li <longli@microsoft.com>
> >
> > For vmbus channels without monitoring support, use kernel UIO
> > interface to indicate packet through interrupt page and UIO file handle.
> >
> > Signed-off-by: Long Li <longli@microsoft.com>
> 
> Something is wrong, no longer applies cleanly.
> $ git am ~/Downloads/bundle-1421-vmbus.mbox
> Applying: net/netvsc: introduce private data for storing vmbus device for
> secondary process
> Applying: net/netvsc: introduce get_vmbus_device to get the vmbus device
> Applying: bus/vmbus: store UIO fd for secondary process
> Applying: bus/vmbus: support channels without monitoring enabled
> Applying: bus/vmbus: add rte_vmbus_device to all functions accessing vmbus
> error: patch failed: drivers/bus/vmbus/vmbus_channel.c:80
> error: drivers/bus/vmbus/vmbus_channel.c: patch does not apply Patch failed at
> 0005 bus/vmbus: add rte_vmbus_device to all functions accessing vmbus

I rebased the patch to net-next and sent v5.

Thanks,
Long

      reply	other threads:[~2025-04-08 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 22:44 [patch v4 0/6] Support VMBUS channels without monitoring enabled longli
2025-04-07 22:44 ` [patch v4 1/6] net/netvsc: introduce private data for storing vmbus device for secondary process longli
2025-04-07 22:45 ` [patch v4 2/6] net/netvsc: introduce get_vmbus_device to get the vmbus device longli
2025-04-07 22:45 ` [patch v4 3/6] bus/vmbus: store UIO fd for secondary process longli
2025-04-07 22:45 ` [patch v4 4/6] bus/vmbus: support channels without monitoring enabled longli
2025-04-07 22:45 ` [patch v4 5/6] bus/vmbus: add rte_vmbus_device to all functions accessing vmbus longli
2025-04-07 22:45 ` [patch v4 6/6] bus/vmbus: set event for channel without monitoring support longli
2025-04-08 14:18   ` Stephen Hemminger
2025-04-08 21:55     ` Long Li [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=SA6PR21MB4231ED0D3C3B0D1684CCE0DACEB52@SA6PR21MB4231.namprd21.prod.outlook.com \
    --to=longli@microsoft.com \
    --cc=dev@dpdk.org \
    --cc=longli@linuxonhyperv.com \
    --cc=stephen@networkplumber.org \
    --cc=weh@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).