From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [announce] [patch] KVM paravirtualization for Linux
Date: Fri, 5 Jan 2007 23:30:09 +0100 [thread overview]
Message-ID: <20070105223009.GA15369@elte.hu> (raw)
In-Reply-To: <459ECDF7.9040309-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
* Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org> wrote:
> What you really want is more like
> EXPORT_SYMBOL_READABLE_GPL(paravirt_ops);
yep. Not a big issue - what is important is to put the paravirt ops into
the read-only section so that it's somewhat harder for rootkits to
modify. (Also, it needs to be made clear that this is fundamental,
lowlevel system functionality written by people under the GPLv2, so that
if you utilize it beyond its original purpose, using its internals, you
likely create a work derived from the kernel. Something simple as irq
disabling probably doesnt qualify, and that we exported to modules for a
long time, but lots of other details do. So the existence of
paravirt_ops isnt a free-for all.)
> But I'm not sure that is technically feasible yet.
>
> The kvm code should probably go in kvm.c instead of paravirt.c.
no. This is fundamental architecture boot code, not module code. kvm.c
should eventually go into kernel/ and arch/*/kernel, not the other way
around.
> Index: linux/drivers/serial/8250.c
> ===================================================================
> --- linux.orig/drivers/serial/8250.c
> +++ linux/drivers/serial/8250.c
> @@ -1371,7 +1371,7 @@ static irqreturn_t serial8250_interrupt(
>
> l = l->next;
>
> - if (l == i->head && pass_counter++ > PASS_LIMIT) {
> + if (!kvm_paravirt
>
> Is this a bug that might happen under other virtualizations as well,
> not just kvm? Perhaps it deserves a disable feature instead of a kvm
> specific check.
yes - this limit is easily triggered via the KVM/Qemu virtual serial
drivers. You can think of "kvm_paravirt" as "Linux paravirt", it's just
a flag.
Ingo
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-01-05 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 21:52 [announce] [patch] KVM paravirtualization for Linux Ingo Molnar
2007-01-05 23:02 ` [kvm-devel] " Anthony Liguori
[not found] ` <20070105215223.GA5361-X9Un+BFzKDI@public.gmane.org>
2007-01-05 22:15 ` Zachary Amsden
[not found] ` <459ECDF7.9040309-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2007-01-05 22:30 ` Ingo Molnar [this message]
[not found] ` <20070105223009.GA15369-X9Un+BFzKDI@public.gmane.org>
2007-01-05 22:50 ` Zachary Amsden
2007-01-05 23:28 ` Ingo Molnar
2007-01-06 13:08 ` Pavel Machek
[not found] ` <20070106130817.GB5660-+ZI9xUNit7I@public.gmane.org>
2007-01-07 18:29 ` Christoph Hellwig
2007-01-08 18:18 ` Christoph Lameter
2007-01-07 12:20 ` Avi Kivity
[not found] ` <45A0E586.50806-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-07 17:42 ` Hollis Blanchard
2007-01-07 17:44 ` Ingo Molnar
[not found] ` <20070107174416.GA14607-X9Un+BFzKDI@public.gmane.org>
2007-01-08 8:22 ` Avi Kivity
[not found] ` <45A1FF4E.1020106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-08 8:39 ` Ingo Molnar
[not found] ` <20070108083935.GB18259-X9Un+BFzKDI@public.gmane.org>
2007-01-08 9:08 ` Avi Kivity
[not found] ` <45A20A0A.70403-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-08 9:18 ` Ingo Molnar
[not found] ` <20070108091819.GB26587-X9Un+BFzKDI@public.gmane.org>
2007-01-08 9:31 ` Avi Kivity
[not found] ` <45A20F60.20207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-08 9:43 ` Ingo Molnar
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=20070105223009.GA15369@elte.hu \
--to=mingo-x9un+bfzkdi@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.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