From: "Glauber de Oliveira Costa" <glommer@gmail.com>
To: "Glauber de Oliveira Costa" <gcosta@redhat.com>
Cc: lguest@ozlabs.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, rusty@rustcorp.com.au,
rostedt@goodmis.org
Subject: Re: [PATCH 0/7] More lguest massage.
Date: Thu, 17 Jan 2008 23:02:42 -0200 [thread overview]
Message-ID: <5d6222a80801171702v5b4ef40ai67b5febd4d74c470@mail.gmail.com> (raw)
In-Reply-To: <12006165841070-git-send-email-gcosta@redhat.com>
I don't have _any_ idea about what happened to those patches. They
were sent through the normal git-send-email script, but for
some reason, all got the same subject. They might be okay for the
review, but anyone willing to try it more seriously, please grab it
at http://glommer.net/patches-lguest.tar.gz
On Jan 17, 2008 10:35 PM, Glauber de Oliveira Costa <gcosta@redhat.com> wrote:
> urrently, lguest module can't be compiled without the PARAVIRT flag being
> on.This is a fake dependency, since the module itself shouldn't need any
> paravirtoverride. Reason for that is the reference to pv_info structure
> ininitial loading tests.
>
> his patch removes it in favour of a more generic error message.
>
> Signed-off-by:Glauber de Oliveira Costa <gcosta@redhat.com>
> ---
> drivers/lguest/core.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff--git a/drivers/lguest/core.c b/drivers/lguest/core.c
> indexbb42fd0..97b76d6 100644
> ---a/drivers/lguest/core.c
> +++b/drivers/lguest/core.c
> @@-255,7 +255,7 @@ static int __init init(void)
>
> /* Lguest can't run under Xen, VMI or itself. It does Tricky Stuff. */
> if (paravirt_enabled()) {
> - printk("lguestis afraid of %s\n", pv_info.name);
> + printk("lguestcan't run under another hypervisor");
> return -EPERM;
> }
>
> --
> 1.5.0.6
>
>
--
Glauber de Oliveira Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
prev parent reply other threads:[~2008-01-18 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 0:35 Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 0:35 ` Glauber de Oliveira Costa
2008-01-18 1:02 ` Glauber de Oliveira Costa [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=5d6222a80801171702v5b4ef40ai67b5febd4d74c470@mail.gmail.com \
--to=glommer@gmail.com \
--cc=gcosta@redhat.com \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®