public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <yasker@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm@vger.kernel.org, avi@redhat.com, jiajun.xu@intel.com,
	sheng@linux.intel.com
Subject: Re: [PATCH 2/2] KVM: x86: Optimize NMI watchdog delivery
Date: Mon, 20 Oct 2008 20:10:06 +0800	[thread overview]
Message-ID: <20081020121006.GC30536@yukikaze> (raw)
In-Reply-To: <20081020082001.912936416@mchn012c.ww002.siemens.net>

On Mon, Oct 20, 2008 at 10:20:03AM +0200, Jan Kiszka wrote:
> As suggested by Avi, this patch introduces a counter of VCPUs that have
> LVT0 set to NMI mode. Only if the counter > 0, we push the PIT ticks via
> all LAPIC LVT0 lines to enable NMI watchdog support.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Acked-by: Sheng Yang <sheng@linux.intel.com>

--
regards
Yang, Sheng
> ---
>  arch/x86/kvm/i8254.c       |   11 ++++++-----
>  arch/x86/kvm/lapic.c       |   23 ++++++++++++++++++++---
>  include/asm-x86/kvm_host.h |    1 +
>  3 files changed, 27 insertions(+), 8 deletions(-)
> 
> Index: b/arch/x86/kvm/i8254.c
> ===================================================================
> --- a/arch/x86/kvm/i8254.c
> +++ b/arch/x86/kvm/i8254.c
> @@ -618,11 +618,12 @@ static void __inject_pit_timer_intr(stru
>  	 * LVT0 to NMI delivery. Other PIC interrupts are just sent to
>  	 * VCPU0, and only if its LVT0 is in EXTINT mode.
>  	 */
> -	for (i = 0; i < KVM_MAX_VCPUS; ++i) {
> -		vcpu = kvm->vcpus[i];
> -		if (vcpu)
> -			kvm_apic_nmi_wd_deliver(vcpu);
> -	}
> +	if (kvm->arch.vapics_in_nmi_mode > 0)
> +		for (i = 0; i < KVM_MAX_VCPUS; ++i) {
> +			vcpu = kvm->vcpus[i];
> +			if (vcpu)
> +				kvm_apic_nmi_wd_deliver(vcpu);
> +		}
>  }
>  
>  void kvm_inject_pit_timer_irqs(struct kvm_vcpu *vcpu)
> Index: b/arch/x86/kvm/lapic.c
> ===================================================================
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -130,6 +130,11 @@ static inline int apic_lvtt_period(struc
>  	return apic_get_reg(apic, APIC_LVTT) & APIC_LVT_TIMER_PERIODIC;
>  }
>  
> +static inline int apic_lvt_nmi_mode(u32 lvt_val)
> +{
> +	return (lvt_val & (APIC_MODE_MASK | APIC_LVT_MASKED)) == APIC_DM_NMI;
> +}
> +
>  static unsigned int apic_lvt_mask[APIC_LVT_NUM] = {
>  	LVT_MASK | APIC_LVT_TIMER_PERIODIC,	/* LVTT */
>  	LVT_MASK | APIC_MODE_MASK,	/* LVTTHMR */
> @@ -672,6 +677,20 @@ static void start_apic_timer(struct kvm_
>  					apic->timer.period)));
>  }
>  
> +static void apic_manage_nmi_watchdog(struct kvm_lapic *apic, u32 lvt0_val)
> +{
> +	int nmi_wd_enabled = apic_lvt_nmi_mode(apic_get_reg(apic, APIC_LVT0));
> +
> +	if (apic_lvt_nmi_mode(lvt0_val)) {
> +		if (!nmi_wd_enabled) {
> +			apic_debug("Receive NMI setting on APIC_LVT0 "
> +				   "for cpu %d\n", apic->vcpu->vcpu_id);
> +			apic->vcpu->kvm->arch.vapics_in_nmi_mode++;
> +		}
> +	} else if (nmi_wd_enabled)
> +		apic->vcpu->kvm->arch.vapics_in_nmi_mode--;
> +}
> +
>  static void apic_mmio_write(struct kvm_io_device *this,
>  			    gpa_t address, int len, const void *data)
>  {
> @@ -753,9 +772,7 @@ static void apic_mmio_write(struct kvm_i
>  		break;
>  
>  	case APIC_LVT0:
> -		if (val == APIC_DM_NMI)
> -			apic_debug("Receive NMI setting on APIC_LVT0 "
> -				"for cpu %d\n", apic->vcpu->vcpu_id);
> +		apic_manage_nmi_watchdog(apic, val);
>  	case APIC_LVTT:
>  	case APIC_LVTTHMR:
>  	case APIC_LVTPC:
> Index: b/include/asm-x86/kvm_host.h
> ===================================================================
> --- a/include/asm-x86/kvm_host.h
> +++ b/include/asm-x86/kvm_host.h
> @@ -359,6 +359,7 @@ struct kvm_arch{
>  	struct kvm_ioapic *vioapic;
>  	struct kvm_pit *vpit;
>  	struct hlist_head irq_ack_notifier_list;
> +	int vapics_in_nmi_mode;
>  
>  	int round_robin_prev_vcpu;
>  	unsigned int tss_addr;
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-10-20 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  8:20 [PATCH 0/2] KVM: x86: Fix and optimize in-kernel NMI watchdog support - v2 Jan Kiszka
2008-10-20  8:20 ` [PATCH 1/2] KVM: x86: Fix and refactor NMI watchdog emulation Jan Kiszka
2008-10-20 12:10   ` Sheng Yang
2008-10-20  8:20 ` [PATCH 2/2] KVM: x86: Optimize NMI watchdog delivery Jan Kiszka
2008-10-20 12:10   ` Sheng Yang [this message]
2008-10-22 10:25 ` [PATCH 0/2] KVM: x86: Fix and optimize in-kernel NMI watchdog support - v2 Avi Kivity

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=20081020121006.GC30536@yukikaze \
    --to=yasker@gmail.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jiajun.xu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=sheng@linux.intel.com \
    /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