From: Roman Kisel <romank@linux.microsoft.com>
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: apais@microsoft.com, benhill@microsoft.com,
bperkins@microsoft.com, sunilmut@microsoft.com, arnd@arndb.de,
bp@alien8.de, catalin.marinas@arm.com, corbet@lwn.net,
dave.hansen@linux.intel.com, decui@microsoft.com,
haiyangz@microsoft.com, hpa@zytor.com, kys@microsoft.com,
mingo@redhat.com, tglx@linutronix.de, wei.liu@kernel.org,
will@kernel.org, x86@kernel.org, linux-hyperv@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH hyperv-next v2 2/4] drivers: hyperv: VMBus protocol version 6.0
Date: Tue, 13 May 2025 09:26:08 -0700 [thread overview]
Message-ID: <96c66528-6149-4f5b-abb1-76b557f47927@linux.microsoft.com> (raw)
In-Reply-To: <d93bebbf-2e0d-4de4-a258-c32159dd1541@oracle.com>
On 5/12/2025 2:49 AM, ALOK TIWARI wrote:
>
>
> On 12-05-2025 04:37, Roman Kisel wrote:
>> The confidential VMBus is supported starting from the protocol
>> version 6.0 onwards.
>>
>> Update the relevant definitions, provide a function that returns
>> whether VMBus is condifential or not.
>
> typo condifential -> confidential
>
>>
>> Signed-off-by: Roman Kisel <romank@linux.microsoft.com>
>> ---
>> drivers/hv/vmbus_drv.c | 12 ++++++
>> include/asm-generic/mshyperv.h | 1 +
>> include/linux/hyperv.h | 71 +++++++++++++++++++++++++---------
>> 3 files changed, 65 insertions(+), 19 deletions(-)
>>
>> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
>> index 1d5c9dcf712e..e431978fa408 100644
>> --- a/drivers/hv/vmbus_drv.c
>> +++ b/drivers/hv/vmbus_drv.c
>> @@ -56,6 +56,18 @@ static long __percpu *vmbus_evt;
>> int vmbus_irq;
>> int vmbus_interrupt;
>> +/*
>> + * If the Confidential VMBus is used, the data on the "wire" is not
>> + * visible to either the host or the hypervisor.
>> + */
>> +static bool is_confidential;
>> +
>> +bool vmbus_is_confidential(void)
>> +{
>> + return is_confidential;
>> +}
>> +EXPORT_SYMBOL_GPL(vmbus_is_confidential);
>> +
>> /*
>> * The panic notifier below is responsible solely for unloading the
>> * vmbus connection, which is necessary in a panic event.
>> diff --git a/include/asm-generic/mshyperv.h b/include/asm-generic/
>> mshyperv.h
>> index 6c51a25ed7b5..96e0723d0720 100644
>> --- a/include/asm-generic/mshyperv.h
>> +++ b/include/asm-generic/mshyperv.h
>> @@ -377,6 +377,7 @@ static inline int hv_call_create_vp(int node, u64
>> partition_id, u32 vp_index, u3
>> return -EOPNOTSUPP;
>> }
>> #endif /* CONFIG_MSHV_ROOT */
>> +bool vmbus_is_confidential(void);
>> #if IS_ENABLED(CONFIG_HYPERV_VTL_MODE)
>> u8 __init get_vtl(void);
>> diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
>> index 1f310fbbc4f9..3cf48f29e6b4 100644
>> --- a/include/linux/hyperv.h
>> +++ b/include/linux/hyperv.h
>> @@ -265,16 +265,19 @@ static inline u32 hv_get_avail_to_write_percent(
>> * Linux kernel.
>> */
>> -#define VERSION_WS2008 ((0 << 16) | (13))
>> -#define VERSION_WIN7 ((1 << 16) | (1))
>> -#define VERSION_WIN8 ((2 << 16) | (4))
>> -#define VERSION_WIN8_1 ((3 << 16) | (0))
>> -#define VERSION_WIN10 ((4 << 16) | (0))
>> -#define VERSION_WIN10_V4_1 ((4 << 16) | (1))
>> -#define VERSION_WIN10_V5 ((5 << 16) | (0))
>> -#define VERSION_WIN10_V5_1 ((5 << 16) | (1))
>> -#define VERSION_WIN10_V5_2 ((5 << 16) | (2))
>> -#define VERSION_WIN10_V5_3 ((5 << 16) | (3))
>> +#define VMBUS_MAKE_VERSION(MAJ, MIN) ((((u32)MAJ) << 16) | (MIN))
>> +#define VERSION_WS2008 VMBUS_MAKE_VERSION(0, 13)
>> +#define VERSION_WIN7 VMBUS_MAKE_VERSION(1, 1)
>> +#define VERSION_WIN8 VMBUS_MAKE_VERSION(2, 4)
>> +#define VERSION_WIN8_1 VMBUS_MAKE_VERSION(3, 0)
>> +#define VERSION_WIN10 VMBUS_MAKE_VERSION(4, 0)
>> +#define VERSION_WIN10_V4_1 VMBUS_MAKE_VERSION(4, 1)
>> +#define VERSION_WIN10_V5 VMBUS_MAKE_VERSION(5, 0)
>> +#define VERSION_WIN10_V5_1 VMBUS_MAKE_VERSION(5, 1)
>> +#define VERSION_WIN10_V5_2 VMBUS_MAKE_VERSION(5, 2)
>> +#define VERSION_WIN10_V5_3 VMBUS_MAKE_VERSION(5, 3)
>> +#define VERSION_WIN_IRON VERSION_WIN10_V5_3
>> +#define VERSION_WIN_COPPER VMBUS_MAKE_VERSION(6, 0)
>> /* Make maximum size of pipe payload of 16K */
>> #define MAX_PIPE_DATA_PAYLOAD (sizeof(u8) * 16384)
>> @@ -335,14 +338,22 @@ struct vmbus_channel_offer {
>> } __packed;
>> /* Server Flags */
>> -#define VMBUS_CHANNEL_ENUMERATE_DEVICE_INTERFACE 1
>> -#define VMBUS_CHANNEL_SERVER_SUPPORTS_TRANSFER_PAGES 2
>> -#define VMBUS_CHANNEL_SERVER_SUPPORTS_GPADLS 4
>> -#define VMBUS_CHANNEL_NAMED_PIPE_MODE 0x10
>> -#define VMBUS_CHANNEL_LOOPBACK_OFFER 0x100
>> -#define VMBUS_CHANNEL_PARENT_OFFER 0x200
>> -#define VMBUS_CHANNEL_REQUEST_MONITORED_NOTIFICATION 0x400
>> -#define VMBUS_CHANNEL_TLNPI_PROVIDER_OFFER 0x2000
>> +#define VMBUS_CHANNEL_ENUMERATE_DEVICE_INTERFACE 0x0001
>> +/*
>> + * This flag indicates that the channel is offered by the paravisor,
>> and must
>> + * use encrypted memory for the channel ring buffer.
>> + */
>> +#define VMBUS_CHANNEL_CONFIDENTIAL_RING_BUFFER 0x0002
>> +/*
>> + * This flag indicates that the channel is offered by the paravisor,
>> and must
>> + * use encrypted memory for GPA direct packets and additional GPADLs.
>> + */
>> +#define VMBUS_CHANNEL_CONFIDENTIAL_EXTERNAL_MEMORY 0x0004
>> +#define VMBUS_CHANNEL_NAMED_PIPE_MODE 0x0010
>> +#define VMBUS_CHANNEL_LOOPBACK_OFFER 0x0100
>> +#define VMBUS_CHANNEL_PARENT_OFFER 0x0200
>> +#define VMBUS_CHANNEL_REQUEST_MONITORED_NOTIFICATION 0x0400
>> +#define VMBUS_CHANNEL_TLNPI_PROVIDER_OFFER 0x2000
>> struct vmpacket_descriptor {
>> u16 type;
>> @@ -621,6 +632,12 @@ struct vmbus_channel_relid_released {
>> u32 child_relid;
>> } __packed;
>> +/*
>> + * Used by the paravisor only, means that the encrypted ring buffers and
>> + * the encrypted external memory are supported
>
> Clearly convey the purpose of the flag, similar to the previous one
> For example ->"Indicates support for encrypted ring buffers and external
> memory, used exclusively by the paravisor."
>
Will do, appreciate your help!!
>> + */
>> +#define VMBUS_FEATURE_FLAG_CONFIDENTIAL_CHANNELS 0x10
>> +
>> struct vmbus_channel_initiate_contact {
>> struct vmbus_channel_message_header header;
>> u32 vmbus_version_requested;
>> @@ -630,7 +647,8 @@ struct vmbus_channel_initiate_contact {
>> struct {
>> u8 msg_sint;
>> u8 msg_vtl;
>> - u8 reserved[6];
>> + u8 reserved[2];
>> + u32 feature_flags; /* VMBus version 6.0 */
>> };
>> };
>> u64 monitor_page1;
>> @@ -1002,6 +1020,11 @@ struct vmbus_channel {
>> /* The max size of a packet on this channel */
>> u32 max_pkt_size;
>> +
>> + /* The ring buffer is encrypted */
>> + bool confidential_ring_buffer;
>> + /* The external memory is encrypted */
>> + bool confidential_external_memory;
>> };
>
> Thanks,
> Alok
>
--
Thank you,
Roman
next prev parent reply other threads:[~2025-05-13 16:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 23:07 [PATCH hyperv-next v2 0/4] Confidential VMBus Roman Kisel
2025-05-11 23:07 ` [PATCH hyperv-next v2 1/4] Documentation: hyperv: " Roman Kisel
2025-05-12 5:22 ` ALOK TIWARI
2025-05-13 16:24 ` Roman Kisel
2025-05-18 21:15 ` Michael Kelley
2025-05-26 16:02 ` Roman Kisel
2025-05-11 23:07 ` [PATCH hyperv-next v2 2/4] drivers: hyperv: VMBus protocol version 6.0 Roman Kisel
2025-05-12 9:49 ` ALOK TIWARI
2025-05-13 16:26 ` Roman Kisel [this message]
2025-05-18 21:15 ` Michael Kelley
2025-05-11 23:07 ` [PATCH hyperv-next v2 3/4] arch: hyperv: Get/set SynIC synth.registers via paravisor Roman Kisel
2025-05-12 9:39 ` ALOK TIWARI
2025-05-13 16:31 ` Roman Kisel
2025-05-18 21:15 ` Michael Kelley
2025-05-11 23:07 ` [PATCH hyperv-next v2 4/4] arch: x86, drivers: hyperv: Enable confidential VMBus Roman Kisel
2025-05-12 13:13 ` ALOK TIWARI
2025-05-13 16:35 ` Roman Kisel
2025-05-18 21:17 ` Michael Kelley
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=96c66528-6149-4f5b-abb1-76b557f47927@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=alok.a.tiwari@oracle.com \
--cc=apais@microsoft.com \
--cc=arnd@arndb.de \
--cc=benhill@microsoft.com \
--cc=bp@alien8.de \
--cc=bperkins@microsoft.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sunilmut@microsoft.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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).