From: nicowisamu <nicowisamu@gmail.com>
To: xen-devel@lists.xensource.com
Subject: consoleio_read in domU
Date: Wed, 8 Feb 2006 18:02:33 +0900 [thread overview]
Message-ID: <78f173a00602080102u9d63153v@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1320 bytes --]
Hello,
I have ported a kernel named toppers on xen as domU using mini-os libraries.
This OS use serial link for display and input.
For printing messages I use the hypercall console_io with the consolio_write
parameter.
For reading the console input I wanted to use the same hypercall with
consolio_read parameter.
But I don't well understand how console sharing works on xen. Because, In
order to call this function I need first
an event from event channel. So, on initializing, I bind VIRQ_CONSOLE with
my handler and then I use the
hypercall to get the message on my buffer. But the handler is never called.
How should I proceed ?
my initialize function where I have replaced the serial initialize by a
bind_virq :
void
serial_initialize(VP_INT portid)
{
static char buf[]="Initializing serial interface";
static char buf2[]=" OK\n";
(void)HYPERVISOR_console_io(CONSOLEIO_write,strlen(buf), buf);
bind_virq(VIRQ_CONSOLE, &serial_handler);
(void)HYPERVISOR_console_io(CONSOLEIO_write,strlen(buf2), buf2);
}
my handler which prints something if it is called :
void
serial_handler(void)
{
//hw_serial_handler();
static char buf[]="character received";
(void)HYPERVISOR_console_io(CONSOLEIO_write,strlen(buf), buf);
}
could someone help me please ?
[-- Attachment #1.2: Type: text/html, Size: 1574 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2006-02-08 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 9:02 nicowisamu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-08 10:10 consoleio_read in domU 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=78f173a00602080102u9d63153v@mail.gmail.com \
--to=nicowisamu@gmail.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.