qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: stefano.stabellini@eu.citrix.com, xen-devel@lists.xenproject.org,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH RFC v1] Cleanups + various fixes due to libxl ABI + more logging on errors.
Date: Mon, 29 Jun 2015 15:25:07 -0400	[thread overview]
Message-ID: <1435605913-23826-1-git-send-email-konrad.wilk@oracle.com> (raw)

As I am in the process of syncing the 'dev.config' and Xen's internal
cache of the PCI config space I noticed that some oddities
in the code and figured that having them in would be easier
for me (so I don't have to handle 20 odd patches).

These:
 [PATCH RFC 1/6] xen/pt: Update comments with proper function name.
 [PATCH RFC 2/6] xen/pt: Make xen_pt_msi_set_enable static
 [PATCH RFC 3/6] xen/pt: xen_host_pci_config_read returns -errno, not
 [PATCH RFC 4/6] xen: Print and use errno where applicable.

are quite simple.

The two other ones:
 [PATCH RFC 5/6] xen/pt/msi: Add the register value when printing
 [PATCH RFC 6/6] xen: Add backtrace for serious issues.

are more for adding the proper infrastructure to debug in the field
bugs that may come about.

 hw/xen/xen_pt.c             |  9 ++++++---
 hw/xen/xen_pt.h             |  1 -
 hw/xen/xen_pt_config_init.c |  6 +++---
 hw/xen/xen_pt_msi.c         |  2 +-
 include/hw/xen/xen_common.h |  1 +
 xen-hvm.c                   | 26 ++++++++++++++++++++++----
 6 files changed, 33 insertions(+), 12 deletions(-)

Konrad Rzeszutek Wilk (6):
      xen/pt: Update comments with proper function name.
      xen/pt: Make xen_pt_msi_set_enable static
      xen/pt: xen_host_pci_config_read returns -errno, not -1 on failure
      xen: Print and use errno where applicable.
      xen/pt/msi: Add the register value when printing logging and error messages
      xen: Add backtrace for serious issues.

             reply	other threads:[~2015-06-29 19:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 19:25 Konrad Rzeszutek Wilk [this message]
2015-06-29 19:25 ` [Qemu-devel] [PATCH RFC 1/6] xen/pt: Update comments with proper function name Konrad Rzeszutek Wilk
2015-07-01 12:54   ` Stefano Stabellini
2015-06-29 19:25 ` [Qemu-devel] [PATCH RFC 2/6] xen/pt: Make xen_pt_msi_set_enable static Konrad Rzeszutek Wilk
2015-07-01 12:55   ` Stefano Stabellini
2015-06-29 19:25 ` [Qemu-devel] [PATCH RFC 3/6] xen/pt: xen_host_pci_config_read returns -errno, not -1 on failure Konrad Rzeszutek Wilk
2015-07-01 12:57   ` Stefano Stabellini
2015-06-29 19:25 ` [Qemu-devel] [PATCH RFC 4/6] xen: Print and use errno where applicable Konrad Rzeszutek Wilk
2015-07-01 13:01   ` Stefano Stabellini
2015-07-01 18:22     ` Konrad Rzeszutek Wilk
2015-07-02 11:00       ` Stefano Stabellini
2015-07-02 14:13         ` Konrad Rzeszutek Wilk
2015-06-29 19:25 ` [Qemu-devel] [PATCH RFC 5/6] xen/pt/msi: Add the register value when printing logging and error messages Konrad Rzeszutek Wilk
2015-06-29 19:25 ` [Qemu-devel] [PATCH RFC 6/6] xen: Add backtrace for serious issues Konrad Rzeszutek Wilk
2015-07-01 13:06   ` Stefano Stabellini
2015-07-02 13:50     ` Stefan Hajnoczi

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=1435605913-23826-1-git-send-email-konrad.wilk@oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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).