Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: tglx@kernel.org, linux-kernel@vger.kernel.org,
	Sean Christopherson <seanjc@google.com>,
	Jim Mattson <jmattson@google.com>,
	Binbin Wu <binbin.wu@linux.intel.com>,
	Vishal L Verma <vishal.l.verma@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Rick P Edgecombe <rick.p.edgecombe@intel.com>,
	Binbin Wu <binbin.wu@intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	Paolo Bonzini <bonzini@redhat.com>
Subject: Re: [PATCH v3 1/2] x86/kvm/vmx: Move IRQ/NMI dispatch from KVM into x86 core
Date: Wed, 20 May 2026 16:06:21 -0700	[thread overview]
Message-ID: <20260520230621.GA706311@ax162> (raw)
In-Reply-To: <20260508091829.GO3126523@noisy.programming.kicks-ass.net>

On Fri, May 08, 2026 at 11:18:29AM +0200, Peter Zijlstra wrote:
> 
> Move the VMX interrupt dispatch magic into the x86 core code. This
> isolates KVM from the FRED/IDT decisions and reduces the amount of
> EXPORT_SYMBOL_FOR_KVM().
> 
> Suggested-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Tested-by: "Verma, Vishal L" <vishal.l.verma@intel.com>

I am seeing

  vmlinux.o: warning: objtool: idt_do_interrupt_irqoff+0xe: no-cfi indirect call!

after this landed in -next.

  $ cat arch/x86/configs/repro.config
  CONFIG_CFI=y
  CONFIG_KVM=y
  CONFIG_KVM_INTEL=y

  $ make -skj"$(nproc)" ARCH=x86_64 LLVM=1 mrproper defconfig repro.config vmlinux
  vmlinux.o: warning: objtool: idt_do_interrupt_irqoff+0xe: no-cfi indirect call!

  $ llvm-objdump -drS --disassemble-symbols=idt_do_interrupt_irqoff vmlinux.o

  vmlinux.o:	file format elf64-x86-64

  Disassembly of section .text:

  0000000000001540 <idt_do_interrupt_irqoff>:
      1540: 55                           	pushq	%rbp
      1541: 48 89 e5                     	movq	%rsp, %rbp
      1544: 48 83 e4 f0                  	andq	$-0x10, %rsp
      1548: 6a 18                        	pushq	$0x18
      154a: 55                           	pushq	%rbp
      154b: 9c                           	pushfq
      154c: 6a 10                        	pushq	$0x10
      154e: e8 00 00 00 00               	callq	0x1553 <idt_do_interrupt_irqoff+0x13>
  		000000000000154f:  R_X86_64_PLT32	__x86_indirect_thunk_rdi-0x4
      1553: c9                           	leave
      1554: e9 00 00 00 00               	jmp	0x1559 <idt_do_interrupt_irqoff+0x19>
  		0000000000001555:  R_X86_64_PLT32	__x86_return_thunk-0x4
      1559: cc                           	int3
      155a: cc                           	int3
      155b: cc                           	int3
      155c: cc                           	int3
      155d: cc                           	int3
      155e: cc                           	int3
      155f: cc                           	int3
      1560: 90                           	nop
      1561: 90                           	nop
      1562: 90                           	nop
      1563: 90                           	nop
      1564: 90                           	nop
      1565: 90                           	nop
      1566: 90                           	nop
      1567: 90                           	nop
      1568: 90                           	nop
      1569: 90                           	nop
      156a: 90                           	nop
      156b: 90                           	nop
      156c: 90                           	nop
      156d: 90                           	nop
      156e: 90                           	nop
      156f: 90                           	nop

Cheers,
Nathan

  parent reply	other threads:[~2026-05-20 23:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 15:56 [PATCH 0/2] x86/kvm/vmx: Fix VMX interrupt injection vs hrtimer_rearm_deferred() Peter Zijlstra
2026-04-23 15:56 ` [PATCH 1/2] x86/kvm/vmx: Move IRQ/NMI dispatch from KVM into x86 core Peter Zijlstra
2026-04-23 17:54   ` Xin Li
2026-04-28  9:43   ` Binbin Wu
2026-04-28 11:25     ` Paolo Bonzini
2026-05-01 20:31       ` Peter Zijlstra
2026-05-01 20:37   ` [PATCH v2 " Peter Zijlstra
2026-05-08  2:54     ` Yan Zhao
2026-05-08  8:54       ` Peter Zijlstra
2026-05-08  6:09     ` Binbin Wu
2026-05-08  8:53       ` Peter Zijlstra
2026-05-08  8:56         ` Binbin Wu
2026-05-08  9:18   ` [PATCH v3 " Peter Zijlstra
2026-05-08  9:41     ` Binbin Wu
2026-05-12 22:31     ` Sean Christopherson
2026-05-18  8:12     ` Zhao Liu
2026-05-20 23:06     ` Nathan Chancellor [this message]
2026-05-26  9:06       ` Peter Zijlstra
2026-05-26 19:35         ` Nathan Chancellor
2026-05-26 10:01     ` Bezdeka, Florian
2026-05-26 10:21       ` Peter Zijlstra
2026-05-26 10:42         ` Florian Bezdeka
2026-04-23 15:56 ` [PATCH 2/2] x86/kvm/vmx: Fix VMX vs hrtimer_rearm_deferred() Peter Zijlstra
2026-05-11 12:59   ` David Woodhouse
2026-05-12 22:32     ` Sean Christopherson
2026-05-15 18:15     ` Marc Dionne
2026-05-18  8:01   ` Zhao Liu
2026-05-18  8:16   ` Binbin Wu

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=20260520230621.GA706311@ax162 \
    --to=nathan@kernel.org \
    --cc=binbin.wu@intel.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bonzini@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=tglx@kernel.org \
    --cc=vishal.l.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox