All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>, <x86@kernel.org>
Cc: <pbonzini@redhat.com>, <joro@8bytes.org>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <bp@alien8.de>, <peterz@infradead.org>,
	<hpa@zytor.com>, <thomas.lendacky@amd.com>, <jon.grimm@amd.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [PATCH 0/2] svm: avic: Allow AVIC support on system w/ physical APIC ID > 255
Date: Wed, 10 Nov 2021 04:18:03 -0600	[thread overview]
Message-ID: <20211110101805.16343-1-suravee.suthikulpanit@amd.com> (raw)

Originally, AMD SVM AVIC supports 8-bit host physical APIC ID.
However, newer AMD systems can have physical APIC ID larger than 255,
and AVIC hardware has been extended to support upto the maximum physical
APIC ID available in the system.

This series introduces a helper function in the APIC subsystem to get
the maximum physical APIC ID allowing the SVM AVIC driver to calculate
the number of bits to program the host physical APIC ID in the AVIC
physical APIC ID table entry.

Regards,
Suravee Suthikulpanit

Suravee Suthikulpanit (2):
  x86/apic: Add helper function to get maximum physical APIC ID
  KVM: SVM: Extend host physical APIC ID field to support more than
    8-bit

 arch/x86/include/asm/apic.h |  1 +
 arch/x86/kernel/apic/apic.c |  6 +++++
 arch/x86/kvm/svm/avic.c     | 53 +++++++++++++++++++++++++++++++------
 arch/x86/kvm/svm/svm.c      |  6 +++++
 arch/x86/kvm/svm/svm.h      |  2 +-
 5 files changed, 59 insertions(+), 9 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-11-10 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 10:18 Suravee Suthikulpanit [this message]
2021-11-10 10:18 ` [PATCH 1/2] x86/apic: Add helper function to get maximum physical APIC ID Suravee Suthikulpanit
2021-11-10 10:18 ` [PATCH 2/2] KVM: SVM: Extend host physical APIC ID field to support more than 8-bit Suravee Suthikulpanit
2021-11-10 19:48   ` Sean Christopherson
2021-11-16 10:29     ` Suthikulpanit, Suravee
2021-11-17 13:06   ` Paolo Bonzini
2021-12-01 15:13     ` Suthikulpanit, Suravee

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=20211110101805.16343-1-suravee.suthikulpanit@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jon.grimm@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.