All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Egger" <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com,
	Robert Phillips <rphillips@virtualiron.com>
Subject: stdvga: slow ioreq
Date: Mon, 5 Nov 2007 13:05:04 +0200	[thread overview]
Message-ID: <200711051205.05004.Christoph.Egger@amd.com> (raw)


Hello Ropert!

Since changeset 16285 (xen-staging), I get the following output when I launch
a HVM guest and VGABios is running:

---------------------------------------------------------------------------------------
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa0000 dir:0 ptr:1 
df:0 count:16
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa0020 dir:0 ptr:1 
df:0 count:16
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa0040 dir:0 ptr:1 
df:0 count:16
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa0060 dir:0 ptr:1 
df:0 count:16
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa0080 dir:0 ptr:1 
df:0 count:16
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa00a0 dir:0 ptr:1 
df:0 count:16
[...]
(XEN) intercept.c:172:d1 slow ioreq. type:1 size:1 addr:0xa1fe0 dir:0 ptr:1 
df:0 count:16
------------------------------------------------------------------------------------------

This is not the full output (to keep this mail readable). The address output
starts from 0xa0000 and goes to 0xa1fe0 and it always increases by 0x20.
(So you can generate the full output yourself :)

The output comes from xen/arch/x86/intercept.c, function 
hvm_buffered_io_send().
It is this code snippet:

    /* Return 0 for the cases we can't deal with. */
    if ( (p->addr > 0xffffful) || p->data_is_ptr || p->df || (p->count != 1) )
    {
        gdprintk(XENLOG_DEBUG, "slow ioreq. type:%d size:%"PRIu64" addr:0x%"
                 PRIx64" dir:%d ptr:%d df:%d count:%"PRIu64"\n",
                 p->type, p->size, p->addr, !!p->dir,
                 !!p->data_is_ptr, !!p->df, p->count);
        return 0;
    }

It looks like the problem was there before changeset 16285 but got uncovered
with the addition of the debug output.

Christoph


-- 
AMD Saxony, Dresden, Germany
Operating System Research Center

Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
   Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
   AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
   Dr. Hans-R. Deppe, Thomas McCoy

             reply	other threads:[~2007-11-05 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 11:05 Christoph Egger [this message]
     [not found] ` <d2cf600d0711050838o637123c1r9e99f49748ea1248@mail.gmail.com>
2007-11-05 16:56   ` stdvga: slow ioreq Christoph Egger
2007-11-05 17:10     ` Keir Fraser
     [not found]     ` <1b64e7ec0711060826s68fe4813o16aba047f18a563c@mail.gmail.com>
2007-11-08 12:49       ` Christoph Egger
2007-11-15 14:58         ` Christoph Egger
2007-11-15 15:08           ` Keir Fraser
2007-11-16 11:01             ` Christoph Egger
2007-11-16 13:52               ` Keir Fraser

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=200711051205.05004.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=rphillips@virtualiron.com \
    --cc=xen-devel@lists.xensource.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.