From: Anthony Liguori <anthony@codemonkey.ws>
To: Richard <judicator3@gmail.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: console driver - How domain0 processes console messages ?
Date: Wed, 16 Feb 2005 19:26:24 -0600 [thread overview]
Message-ID: <4213F2C0.5000706@codemonkey.ws> (raw)
In-Reply-To: <eacc82a40502160135344eeb1@mail.gmail.com>
>> Next, I am going to look at tools/python/xen/lowlevel/xu/xu.c to see
>>if domain0 is receiving the actual data being sent from mini-os
>>console driver.
>>
>>
>
>Sounds like a plan. I'd thing that you should be able to pull most of
>the control ring interaction code straight out of the console driver.
>
>
With xcs you can run a utility called xcsdump which will show you most
of the control traffic going on in your system.
The easiest thing to do though would probably be to launch vm-create
(part of vm-tools) with the -i option (interactive) and just step
through it with gdb.
The message flow isn't terribly obvious just by looking at the code
however it should be quite understandable in gdb.
Let me know when you get to implementing support for virtual devices (if
you do). I've got all sorts of xcs/xu debugging stuff that I'm going to
eventually clean-up and submit. They're pretty granular for most of the
important messages (dumping out every field in all the messages).
Good luck :-)
Regards,
>good luck!
>a.
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
--
Anthony Liguori
anthony@codemonkey.ws
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-17 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 6:10 console driver - How domain0 processes console messages ? Richard
2005-02-16 7:54 ` Andrew Warfield
2005-02-16 8:38 ` Richard
2005-02-16 9:35 ` Andrew Warfield
2005-02-17 1:26 ` Anthony Liguori [this message]
2005-02-21 3:04 ` Richard
2005-02-16 8:38 ` aq
[not found] ` <eacc82a405021600562ed346d2@mail.gmail.com>
2005-02-16 8:57 ` Andrew Warfield
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=4213F2C0.5000706@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=judicator3@gmail.com \
--cc=xen-devel@lists.sourceforge.net \
/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.