[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEt2pLgmIUuRJvDa@google.com>
Date: Thu, 12 Jun 2025 17:53:56 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Kai Huang <kai.huang@...el.com>
Cc: "pbonzini@...hat.com" <pbonzini@...hat.com>, "vkuznets@...hat.com" <vkuznets@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 07/18] KVM: x86: Rename irqchip_kernel() to irqchip_full()
On Thu, Jun 12, 2025, Kai Huang wrote:
> On Wed, 2025-06-11 at 14:35 -0700, Sean Christopherson wrote:
> > Rename irqchip_kernel() to irqchip_full(), as "kernel" is very ambiguous
> > due to the existence of split IRQ chip support, where only some of the
> > "irqchip" is in emulated by the kernel/KVM. E.g. irqchip_kernel() often
>
> "is in emulated" -> "is emulated".
>
> Or did you mean:
>
> "is emulated in the kernel/KVM"?
Heh, both? I'll go with "is emulated". IIRC, I was trying to choose between
the two options you listed, and didn't quite get the cleanup right.
Powered by blists - more mailing lists