Re: [RFC PATCH v8 15/35] x86/apic: Unionize apic regs for 32bit/64bit access w/o type casting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 7/12/2025 8:51 PM, Borislav Petkov wrote:
> On Thu, Jul 10, 2025 at 09:13:11AM +0530, Neeraj Upadhyay wrote:
>>     struct secure_apic_page {
>> 	u8 *regs[PAGE_SIZE];
>>     } __aligned(PAGE_SIZE);
>>
>>
>> to
>>
>>     struct secure_apic_page {
> 
> secure_apic_page or secure_aVic_page?
>

In v8, the struct was named "apic_page". Sean's suggested to use "secure_apic_page"
to avoid name conflicts with other apic code. APM calls it "guest APIC backing page" -
guest-owned page containing APIC state.
 
> I mean, what is a secure APIC?
> 

It was more to imply like secure APIC-page rather than Secure-APIC page. I will change
it to secure_avic_page or savic_apic_page, if one of these looks cleaner. Please suggest.


- Neeraj







[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux