qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio device error reporting best practice?
Date: Mon, 17 Mar 2014 15:50:39 +0100	[thread overview]
Message-ID: <1395067839.5663.16.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <CAPM=9twJX3F+as1TuoerW1Yt-b0xw8YEf1YHa0B+MLMJBd0i_w@mail.gmail.com>

On Mo, 2014-03-17 at 16:02 +1000, Dave Airlie wrote:
> So I'm looking at how best to do virtio gpu device error reporting,
> and how to deal with illegal stuff,
> 
> I've two levels of errors I want to support,
> 
> a) unrecoverable or bad guest kernel programming errors,
> 
> b) per 3D context errors from the renderer backend,

What you find in modern real hardware (xhci for example) and which would
also make sense for virtio is:

 * stick an error message into a event queue (for non-fatal errors),
   which would be a good fit for (b)
 * set a bit in a error status register, maybe raise IRQ, stop
   processing until reset (for fatal errors, i.e. your (a) case).
   such a register can live in config space for virtio.

cheers,
  Gerd

  parent reply	other threads:[~2014-03-17 14:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17  6:02 [Qemu-devel] virtio device error reporting best practice? Dave Airlie
2014-03-17 14:28 ` Laszlo Ersek
2014-03-17 14:40   ` Peter Maydell
2014-03-17 14:49     ` Laszlo Ersek
2014-03-17 14:54       ` Peter Maydell
2014-03-17 14:57       ` Gerd Hoffmann
2014-03-17 19:05       ` Andreas Färber
2014-03-18 12:45       ` Kevin Wolf
2014-03-17 14:57     ` Richard W.M. Jones
2014-03-17 14:59       ` Richard W.M. Jones
2014-03-26 12:49   ` Stefan Hajnoczi
2014-03-17 14:50 ` Gerd Hoffmann [this message]
2014-03-19  0:34 ` Rusty Russell
2014-03-19  8:12   ` Markus Armbruster
2014-03-20  3:40     ` Rusty Russell
2014-03-20  6:39       ` Markus Armbruster
2014-03-20 12:53         ` Peter Maydell
2014-03-26 14:34           ` Markus Armbruster
2014-03-27  0:54             ` Venkatesh Srinivas
2014-03-20  6:51   ` Michael S. Tsirkin
2014-03-21  9:44     ` Yan Vugenfirer

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=1395067839.5663.16.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=airlied@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).