[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <296e1196-9572-4839-9298-002d6c52537c@intel.com>
Date: Mon, 11 Mar 2024 14:05:38 +1300
From: "Huang, Kai" <kai.huang@...el.com>
To: Isaku Yamahata <isaku.yamahata@...ux.intel.com>, Sean Christopherson
<seanjc@...gle.com>
CC: David Matlack <dmatlack@...gle.com>, "kvm@...r.kernel.org"
<kvm@...r.kernel.org>, Isaku Yamahata <isaku.yamahata@...el.com>,
"federico.parola@...ito.it" <federico.parola@...ito.it>,
"pbonzini@...hat.com" <pbonzini@...hat.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "isaku.yamahata@...il.com"
<isaku.yamahata@...il.com>, "michael.roth@....com" <michael.roth@....com>
Subject: Re: [RFC PATCH 1/8] KVM: Document KVM_MAP_MEMORY ioctl
>
> struct kvm_memory_mapping {
> __u64 base_gfn;
> __u64 nr_pages;
> __u64 flags;
> __u64 source;
> };
From your next patch the @source must be 4K aligned. If it is intended
please document this too.
[...]
The backend may encrypt
> it.
To me the "backend" is a little bit confusing. It doesn't mean the
@source, correct? Maybe just the "underlying physical pages may be
encrypted" etc. But it may be only my issue.
Powered by blists - more mailing lists