From: kuas <ku4s@users.sourceforge.net>
To: xen-devel-ml <xen-devel@lists.sourceforge.net>
Subject: xm dmesg and performance on serial port
Date: Mon, 25 Oct 2004 02:30:14 -0400 [thread overview]
Message-ID: <417C9D76.70400@users.sourceforge.net> (raw)
Hello,
I might only have configuration problem, but I couldn't find any docs
that could relate to the problem. The command: 'xm dmesg' seems to stop
buffering any output after a while. I have to enable serial port to get
the output bigger than the buffer. I don't know how big the buffer or if
it's circular? Is there anyway to fix this behavior?
The second question I have since I have to enable the serial line.
Considering the speed of the serial line is very slow. Would that affect
the performance of XEN than just buffering the output (for 'xm dmesg')?
I do have to output some messages when a certain event occurs. Will
enabling more consoles (serials, vga, tty) slow the performance by default?
Just by reading the XEN papers, XEN has a way to register asynchronous
events to the domains. Would it be better in terms of performance to
send the event messages to a particular domain (e.g: Domain 0) using the
asynchronous mechanism and have the domain kernel to handle the messages
as XEN events.
Thanks in advance for any comments.
Kuas.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next reply other threads:[~2004-10-25 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 6:30 kuas [this message]
2004-10-25 18:08 ` xm dmesg and performance on serial port Mark A. Williamson
2004-10-26 4:05 ` kuas
2004-11-01 0:29 ` Mark A. Williamson
2004-10-25 18:13 ` 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=417C9D76.70400@users.sourceforge.net \
--to=ku4s@users.sourceforge.net \
--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.