qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: aik@ozlabs.ru, qiudayu@linux.vnet.ibm.com,
	Gavin Shan <gwshan@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1 1/3] sPAPR: Implement PCI error injection RTAS calls
Date: Tue, 24 Jun 2014 07:03:54 +1000	[thread overview]
Message-ID: <1403557434.4587.134.camel@pasglop> (raw)
In-Reply-To: <53A8535D.1080209@suse.de>

On Mon, 2014-06-23 at 18:18 +0200, Alexander Graf wrote:
> Device emulation code shouldn't even remotely have an idea what host 
> it's running on. Also semantically there are a few issues with this approach
> 
>    1) QEMU is usually running with user privileges, so it doesn't have 
> access to the file above

Right, this needs to go via VFIO like the rest of the EEH stuff

>    2) QEMU's channel to hardware devices is via normal kernel API. For 
> physical devices that's VFIO. No side channels please.

Indeed. If the user gets access to that file, suddenly qemu can
"manufacture" a bad string and error inject in other devices it doesn't
own which isn't great.

Gavin, this needs to go via the same path as normal EEH and be limited
to injecting errors that are completely bounded to the PE.

I don't think this is very high priority. We should first write a good
host side error injection tool and sort out the reporting of the EEH log
from host to guest.

>    3) Ownership of the question whether a PE is in error mode is 
> responsibility of the PHB. In the emulated case, the PHB would have to 
> set itself into a mode where it behaves as if it's blocked.

We don't have to support error injection for emulated since we don't
support (yet) the rest oF EEH for them. We could one day but it's
really not urgent.

Cheers,
Ben.

  reply	other threads:[~2014-06-23 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23  2:22 [Qemu-devel] [PATCH v1 0/3] Support PCI Error Injection Gavin Shan
2014-06-23  2:22 ` [Qemu-devel] [PATCH v1 1/3] sPAPR: Implement PCI error injection RTAS calls Gavin Shan
2014-06-23 16:18   ` Alexander Graf
2014-06-23 21:03     ` Benjamin Herrenschmidt [this message]
2014-06-23 21:13       ` Alexander Graf
2014-06-24  0:14         ` Gavin Shan
2014-06-24  0:58     ` Gavin Shan
2014-06-23  2:22 ` [Qemu-devel] [PATCH v1 2/3] sPAPR: Implement sPAPRPHBClass::format_errinjct_cmd Gavin Shan
2014-06-23  2:22 ` [Qemu-devel] [PATCH v1 3/3] sPAPR: Export RTAS property <ibm, errinjct-tokens> Gavin Shan

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=1403557434.4587.134.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qiudayu@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).