xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH QEMU-upstream] xen: fix two errors when debug is enabled
Date: Fri, 1 Nov 2013 16:01:29 +0000	[thread overview]
Message-ID: <20131101160129.GI4966@zion.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310151156530.26077@kaball.uk.xensource.com>

On Tue, Oct 15, 2013 at 11:57:01AM +0100, Stefano Stabellini wrote:
> On Mon, 14 Oct 2013, Wei Liu wrote:
> > This patch fixes:
> > 1. build error in xen_pt.c when XEN_PT_LOGGING_ENABLED is defined
> > 2. debug output format string error when DEBUG_XEN is defined
> > 
> > In the second case I also have the output info in consistent with the
> > output in mapping function - that is, print start_addr instead of
> > phys_offset.
> > 
> > Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it>
> > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> > Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> > Cc: Anthony Perard <anthony.perard@citrix.com>
> 
> Looks good.
> 

I take it as an Acked-by.

I seem to have forgotten CC qemu-devel. Should I resend it to
qemu-devel? Or are you going to send it via git pull?

Wei.

> 
> >  hw/xen/xen_pt.c |    3 ++-
> >  xen-all.c       |    4 ++--
> >  2 files changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
> > index ca2d460..d58cb61 100644
> > --- a/hw/xen/xen_pt.c
> > +++ b/hw/xen/xen_pt.c
> > @@ -570,7 +570,8 @@ static void xen_pt_region_update(XenPCIPassthroughState *s,
> >      if (args.rc) {
> >          XEN_PT_WARN(d, "Region: %d (addr: %#"FMT_PCIBUS
> >                      ", len: %#"FMT_PCIBUS") is overlapped.\n",
> > -                    bar, sec->offset_within_address_space, sec->size);
> > +                    bar, sec->offset_within_address_space,
> > +                    int128_get64(sec->size));
> >      }
> >  
> >      if (d->io_regions[bar].type & PCI_BASE_ADDRESS_SPACE_IO) {
> > diff --git a/xen-all.c b/xen-all.c
> > index 9a27899..4a594bd 100644
> > --- a/xen-all.c
> > +++ b/xen-all.c
> > @@ -369,8 +369,8 @@ static int xen_remove_from_physmap(XenIOState *state,
> >      phys_offset = physmap->phys_offset;
> >      size = physmap->size;
> >  
> > -    DPRINTF("unmapping vram to %"HWADDR_PRIx" - %"HWADDR_PRIx", from ",
> > -            "%"HWADDR_PRIx"\n", phys_offset, phys_offset + size, start_addr);
> > +    DPRINTF("unmapping vram to %"HWADDR_PRIx" - %"HWADDR_PRIx", at "
> > +            "%"HWADDR_PRIx"\n", start_addr, start_addr + size, phys_offset);
> >  
> >      size >>= TARGET_PAGE_BITS;
> >      start_addr >>= TARGET_PAGE_BITS;
> > -- 
> > 1.7.10.4
> > 

  reply	other threads:[~2013-11-01 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 12:53 [PATCH QEMU-upstream] xen: fix two errors when debug is enabled Wei Liu
2013-10-15 10:57 ` Stefano Stabellini
2013-11-01 16:01   ` Wei Liu [this message]
2013-11-06 17:20     ` Stefano Stabellini
2013-11-25  9:56       ` Fabio Fantoni

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=20131101160129.GI4966@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).