[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87tuv4uwmt.fsf@nanos.tec.linutronix.de>
Date: Fri, 09 Oct 2020 01:27:06 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: David Woodhouse <dwmw2@...radead.org>, x86@...nel.org
Cc: kvm <kvm@...r.kernel.org>, Paolo Bonzini <pbonzini@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 5/5] x86/kvm: Add KVM_FEATURE_MSI_EXT_DEST_ID
On Thu, Oct 08 2020 at 22:39, David Woodhouse wrote:
> On Thu, 2020-10-08 at 23:14 +0200, Thomas Gleixner wrote:
>> >
>> > (We'd want the x86_vector_domain to actually have an MSI compose
>> > function in the !CONFIG_PCI_MSI case if we did this, of course.)
>>
>> The compose function and the vector domain wrapper can simply move to
>> vector.c
>
> I ended up putting __irq_msi_compose_msg() into apic.c and that way I
> can make virt_ext_dest_id static in that file.
>
> And then I can move all the HPET-MSI support into hpet.c too.
Works for me.
> https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/ext_dest_id
For the next submission, can you please
- pick up the -ENODEV changes for HPET/IOAPIC which I posted earlier
- shuffle all that compose/IOAPIC cleanup around
before adding that extended dest id stuff.
Thanks,
tglx
Powered by blists - more mailing lists