[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC 01/10] x86: introduce AMD-V and Intel VT-x Kconfig options
- To: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Tue, 14 Feb 2023 08:48:07 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=jbyW7g/n2hz4XkVGlKoGQ7/VCjoSFDzdx34OPekR/zk=; b=GYsQC1iajxG9Y9HiKOJtsS1SFzXz08VmkSiUr6D6S98ggF+jNiQN7Mon7nV3WZ+OZ9e/fUFFQXKnb9gi8KOtZ1JihJzlzOzQIDDhAJjUQh+ujpHzXBh6dgVGgpUMWqlJy2sDa0RFJVpdNUB3JC44qkULWL0wQcBUyGHVpFLzk6IpNNML5oDqf8IirEPvn+rkCn0TLxKz/AbXLZ6oktdwc5zQ9Pw0tjQn5rSTPCDYgyzJpUu+rJTAy5U7JSW2DnzEq4/qE0mvSLkgwcWa3O5RfgiQFAA9cEYUymFuYjLNZU2AU/WmQUrIHGc3fqzwykADIk4HdpAtLRPDFqe1wSH92g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Y+4p066Guek49K9MYPxzeN6rb87fId9rKYc64gQ1TeWrGh2NOMtjU6UL+BH7XXeGGI9bIromLINUkhgUdvCa0I8y9G833mTQHQPRdiTxI0Aytr8qM41Mo/WMvuWQIZGQwnusCtWuGbEKGCdcyEHXywma2Tmcn90zfdNiNruVYW/PuSlZ9oBAOs4tZ9cJ+UldkcKMDStpi54ijlGJp1w5AcavLeon4Nov9qjDyVEnq7/y1m92O+yD6daz8c2fKBl4NeM4z+H9Y5jSEmkdgcwKdatEJAkQnIBkrrAzIf6b4+P3hsvwR9go6Kll56VHK2aI8rH0ouhzyXVFj2Y5OucQcA==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Xenia Ragiadakou <burzalodowa@xxxxxxxxx>, Wei Liu <wl@xxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Paul Durrant <paul@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Tue, 14 Feb 2023 07:49:01 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 13.02.2023 21:53, Boris Ostrovsky wrote:
>
> On 2/13/23 11:41 AM, Jan Beulich wrote:
>> On 13.02.2023 17:30, Xenia Ragiadakou wrote:
>>> On 2/13/23 17:11, Jan Beulich wrote:
>>>> On 13.02.2023 15:57, Xenia Ragiadakou wrote:
>>>>> --- a/xen/arch/x86/cpu/Makefile
>>>>> +++ b/xen/arch/x86/cpu/Makefile
>>>>> @@ -10,4 +10,6 @@ obj-y += intel.o
>>>>> obj-y += intel_cacheinfo.o
>>>>> obj-y += mwait-idle.o
>>>>> obj-y += shanghai.o
>>>>> -obj-y += vpmu.o vpmu_amd.o vpmu_intel.o
>>>>> +obj-y += vpmu.o
>>>>> +obj-$(CONFIG_AMD_SVM) += vpmu_amd.o
>>>>> +obj-$(CONFIG_INTEL_VMX) += vpmu_intel.o
>>>> This code was moved from hvm/ to cpu/ for the specific reason of also
>>>> being used by PV guests. (Sadly the comments at the top weren't
>>>> corrected at that time.)
>>> Hmm, the init functions are prefixed with svm/vmx.
>>> Does vpmu depend on svm/vmx support?
>> There are interactions, but I don't think there's a dependency. You
>> may want to ask Boris (whom I have now added to Cc).
>
> MSR intercept bits need to be manipulated, which is SVM/VMX-specific.
But that's "interaction", not "dependency" aiui: The intercept bits aren't
relevant for PV guests, are they?
Jan
|
