From: Rusty Russell <rusty@rustcorp.com.au>
To: James Morris <jmorris@namei.org>
Cc: virtualization@lists.osdl.org
Subject: Re: [LGUEST] updated nohz/hrtimer WIP patches (v04)
Date: Fri, 30 Mar 2007 12:08:21 +1000 [thread overview]
Message-ID: <1175220502.12230.355.camel@localhost.localdomain> (raw)
In-Reply-To: <Line.LNX.4.64.0703291151270.12641@d.namei>
On Thu, 2007-03-29 at 11:53 -0400, James Morris wrote:
> At http://namei.org/misc/lguest/patches/time/v04/
>
> Just a resync to the latest upstream lguest patch queue, after some fun
> with bare metal bugs and assorted churn.
Hi James!
Thanks for the patch! Nothing major to add, just some questions
mainly...
> diff --git a/drivers/lguest/core.c b/drivers/lguest/core.c
> index d8f136a..344b455 100644
> --- a/drivers/lguest/core.c
> +++ b/drivers/lguest/core.c
> @@ -393,6 +393,23 @@ int find_free_guest(void)
> return -1;
> }
>
> +void guest_clockevent(struct lguest *lg, const ktime_t __user *u)
interrupts_and_traps.c might be a better place for this? Similarly the
code currently in lguest_user.c, which is mainly for code dealing
with /dev/lguest.
> + case LHCALL_CLOCKEVENT:
> + guest_clockevent(lg, (ktime_t __user *)regs->edx);
> + break;
Perhaps LHCALL_SET_CLOCKEVENT is a better name? Or were you thinking of
extending it?
> --- a/drivers/lguest/lguest.c
> +++ b/drivers/lguest/lguest.c
> @@ -62,6 +64,7 @@ #include <asm/e820.h>
> #include <asm/pda.h>
> #include <asm/asm-offsets.h>
> #include <asm/mce.h>
> +#include "lg.h"
Hmm, this implies we've knotted the headers somehow. "lg.h" is supposed
to be the internal header for lg.ko. Perhaps something needs to be
moved to linux/lguest.h?
Thanks!
Rusty.
prev parent reply other threads:[~2007-03-30 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 16:11 [LGUEST] updated nohz/hrtimer WIP patches (v02) James Morris
2007-03-29 15:53 ` [LGUEST] updated nohz/hrtimer WIP patches (v04) James Morris
2007-03-29 16:45 ` Jeremy Fitzhardinge
2007-03-29 19:15 ` James Morris
2007-03-29 19:24 ` Jeremy Fitzhardinge
2007-03-30 2:08 ` Rusty Russell [this message]
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=1175220502.12230.355.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=jmorris@namei.org \
--cc=virtualization@lists.osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).