All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacob@melon.dk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen list <xen-devel@lists.sourceforge.net>
Subject: Re: HYPERVISOR_console_write gone?
Date: Wed, 10 Mar 2004 13:20:08 +0100	[thread overview]
Message-ID: <1078921208.612.23.camel@jacobg> (raw)
In-Reply-To: <E1B0o0x-00077G-00@wisbech.cl.cam.ac.uk>

On Tue, 2004-03-09 at 21:39, Keir Fraser wrote:

> Guest OSes should send their console output via domain 0
> now. HYPERVISOR_console_write is still available in debug builds -- if
> you want this capability without a full debug build of Xen then you
> will need to manually edit common/console.c.

How do I configure my guest OS to send printks to dom0? I used to have
the #if 1 thing set in kernel/printk.c, but that is gone now. My
unprivileged domains have gone awfully quiet now.

Btw, there is no common/console.c in neither Xen nor Xenolinux. I would
really like to have HYPERVISOR_console_write back, so I have re-added
the definition to asm/hypervisor.h. What do I have to change in Xen (I
don't think I want a full debug build) to make it work?

Lastly, I used to be able to interact with Xen via the serial line, but
it seems to no longer listen to my keypresses. How do I reenable that?

thanks in advance,
Jacob



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-10 12:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 15:54 HYPERVISOR_console_write gone? Jacob Gorm Hansen
2004-03-09 20:39 ` Keir Fraser
2004-03-10 12:20   ` Jacob Gorm Hansen [this message]
2004-03-10 12:27     ` Jacob Gorm Hansen
2004-03-10 12:38     ` Jacob Gorm Hansen
2004-03-10 12:44       ` Ian Pratt
2004-03-10 13:20         ` Jacob Gorm Hansen
2004-03-10 13:32           ` Ian Pratt
2004-03-10 13:48             ` Jacob Gorm Hansen
2004-03-10 14:33               ` Keir Fraser
2004-03-10 14:35               ` Ian Pratt

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=1078921208.612.23.camel@jacobg \
    --to=jacob@melon.dk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.