From: David Miller <davem@davemloft.net>
To: grantr@vmware.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
pv-drivers@vmware.com
Subject: Re: [PATCH] VSOCK: Support VM sockets connected to the hypervisor.
Date: Fri, 15 Mar 2013 08:25:30 -0400 (EDT) [thread overview]
Message-ID: <20130315.082530.1920500635070584515.davem@davemloft.net> (raw)
In-Reply-To: <1363117219-21911-1-git-send-email-grantr@vmware.com>
From: Reilly Grant <grantr@vmware.com>
Date: Tue, 12 Mar 2013 12:40:19 -0700
> The resource ID used for VM socket control packets (0) is already
> used for the VMCI_GET_CONTEXT_ID hypercall so a new ID (15) must be
> used when the guest sends these datagrams to the hypervisor.
>
> The hypervisor context ID must also be removed from the internal
> blacklist.
>
> Signed-off-by: Reilly Grant <grantr@vmware.com>
> Acked-by: Andy King <acking@vmware.com>
Applied, thanks.
prev parent reply other threads:[~2013-03-15 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 19:40 [PATCH] VSOCK: Support VM sockets connected to the hypervisor Reilly Grant
2013-03-14 21:55 ` [PATCH v2] " Reilly Grant
2013-03-15 12:25 ` David Miller [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=20130315.082530.1920500635070584515.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grantr@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.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