From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xend leaks/bugs/etc
Date: Wed, 20 Apr 2005 00:10:55 -0700 [thread overview]
Message-ID: <4266007F.2060405@diku.dk> (raw)
In-Reply-To: <1113846797.9390.15.camel@localhost.localdomain>
Hollis Blanchard wrote:
> When the ring queue overflows, console data will be dropped, which is
> significant. I notice you avoided the subject of a shared-memory video
> protocol: in that case, dropped data could leave parts of the screen
> obsolete.
The same thing happens on a VGA console today, lets not make things
harder in Xen than they are in real life. If you want to be sure that
you see everything (human operator reading bandwidth is also fairly
limited btw.) setup a system which logs stuff to a file inside the VM.
Jacob
next prev parent reply other threads:[~2005-04-20 7:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 15:42 xend leaks/bugs/etc Ian Pratt
2005-04-18 6:00 ` Allen Short
2005-04-18 14:32 ` Harry Butterworth
2005-04-18 15:15 ` Anthony Liguori
2005-04-18 15:27 ` Hollis Blanchard
2005-04-18 15:45 ` Anthony Liguori
2005-04-18 16:16 ` Hollis Blanchard
2005-04-18 16:49 ` Harry Butterworth
2005-04-18 18:01 ` Anthony Liguori
2005-04-18 17:53 ` Hollis Blanchard
2005-04-20 7:10 ` Jacob Gorm Hansen [this message]
2005-04-20 14:16 ` Anthony Liguori
2005-04-21 22:58 ` Jacob Gorm Hansen
2005-04-22 0:21 ` Anthony Liguori
2005-04-18 15:58 ` Harry Butterworth
2005-04-18 21:33 ` Mike D. Day
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 23:12 Ian Pratt
2005-04-20 7:54 ` Jacob Gorm Hansen
2005-04-20 14:34 ` Hollis Blanchard
2005-04-16 18:08 Allen Short
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=4266007F.2060405@diku.dk \
--to=jacobg@diku.dk \
--cc=hollisb@us.ibm.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.