All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: gleb@kernel.org, agraf@suse.de, kvm-ppc@vger.kernel.org,
	paulus@ozlabs.org, linuxppc-dev@ozlabs.org, pbonzini@redhat.com,
	mahesh@linux.vnet.ibm.com, david@gibson.dropbear.id.au,
	kvm@vger.kernel.org
Subject: Re: [PATCH v4 1/2] KVM: PPC: Add new capability to control MCE behaviour
Date: Tue, 10 Jan 2017 02:36:28 +0000	[thread overview]
Message-ID: <20170110022428.GA7781@localhost.localdomain> (raw)
In-Reply-To: <148396203530.1471.16105350692124392705.stgit@aravinda>

On Mon, Jan 09, 2017 at 05:10:35PM +0530, Aravinda Prasad wrote:
> This patch introduces a new KVM capability to control
> how KVM behaves on machine check exception (MCE).
> Without this capability, KVM redirects machine check
> exceptions to guest's 0x200 vector, if the address in
> error belongs to the guest. With this capability KVM
> causes a guest exit with NMI exit reason.
>
> The new capability is required to avoid problems if
> a new kernel/KVM is used with an old QEMU for guests
> that don't issue "ibm,nmi-register". As old QEMU does
> not understand the NMI exit type, it treats it as a
> fatal error. However, the guest could have handled
> the machine check error if the exception was delivered
> to guest's 0x200 interrupt vector instead of NMI exit
> in case of old QEMU.
> 

Can you move these to a cover letter, the description
here does not match the changes
 
> QEMU part can be found at:
> http://lists.nongnu.org/archive/html/qemu-ppc/2015-12/msg00199.html
>

Balbir Singh. 

WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <bsingharora@gmail.com>
To: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: gleb@kernel.org, agraf@suse.de, kvm-ppc@vger.kernel.org,
	paulus@ozlabs.org, linuxppc-dev@ozlabs.org, pbonzini@redhat.com,
	mahesh@linux.vnet.ibm.com, david@gibson.dropbear.id.au,
	kvm@vger.kernel.org
Subject: Re: [PATCH v4 1/2] KVM: PPC: Add new capability to control MCE behaviour
Date: Tue, 10 Jan 2017 07:54:28 +0530	[thread overview]
Message-ID: <20170110022428.GA7781@localhost.localdomain> (raw)
In-Reply-To: <148396203530.1471.16105350692124392705.stgit@aravinda>

On Mon, Jan 09, 2017 at 05:10:35PM +0530, Aravinda Prasad wrote:
> This patch introduces a new KVM capability to control
> how KVM behaves on machine check exception (MCE).
> Without this capability, KVM redirects machine check
> exceptions to guest's 0x200 vector, if the address in
> error belongs to the guest. With this capability KVM
> causes a guest exit with NMI exit reason.
>
> The new capability is required to avoid problems if
> a new kernel/KVM is used with an old QEMU for guests
> that don't issue "ibm,nmi-register". As old QEMU does
> not understand the NMI exit type, it treats it as a
> fatal error. However, the guest could have handled
> the machine check error if the exception was delivered
> to guest's 0x200 interrupt vector instead of NMI exit
> in case of old QEMU.
> 

Can you move these to a cover letter, the description
here does not match the changes
 
> QEMU part can be found at:
> http://lists.nongnu.org/archive/html/qemu-ppc/2015-12/msg00199.html
>

Balbir Singh. 

  parent reply	other threads:[~2017-01-10  2:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 11:40 [PATCH v4 1/2] KVM: PPC: Add new capability to control MCE behaviour Aravinda Prasad
2017-01-09 11:52 ` Aravinda Prasad
2017-01-09 11:40 ` Aravinda Prasad
2017-01-09 11:40 ` [PATCH v4 2/2] KVM: PPC: Exit guest upon MCE when FWNMI capability is enabled Aravinda Prasad
2017-01-09 11:52   ` Aravinda Prasad
2017-01-12  3:16   ` David Gibson
2017-01-12  3:16     ` David Gibson
2017-01-12  3:16     ` David Gibson
2017-01-12  9:05   ` Balbir Singh
2017-01-12  9:17     ` Balbir Singh
2017-01-12 10:14     ` Aravinda Prasad
2017-01-12 10:26       ` Aravinda Prasad
2017-01-10  2:24 ` Balbir Singh [this message]
2017-01-10  2:36   ` [PATCH v4 1/2] KVM: PPC: Add new capability to control MCE behaviour Balbir Singh
2017-01-12  9:56 ` Paul Mackerras
2017-01-12  9:56   ` Paul Mackerras
2017-01-12  9:56   ` Paul Mackerras
2017-01-13  7:22   ` Aravinda Prasad
2017-01-13  7:34     ` Aravinda Prasad
2017-01-13  7:22     ` Aravinda Prasad

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=20170110022428.GA7781@localhost.localdomain \
    --to=bsingharora@gmail.com \
    --cc=agraf@suse.de \
    --cc=aravinda@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=gleb@kernel.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=paulus@ozlabs.org \
    --cc=pbonzini@redhat.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 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.