From: Anthony Liguori <anthony@codemonkey.ws>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [kvm-devel] [PATCH 3/3] KVM paravirt-ops implementation
Date: Wed, 29 Aug 2007 00:53:15 -0500 [thread overview]
Message-ID: <1188366795.6337.11.camel@squirrel> (raw)
In-Reply-To: <1188325890.5531.78.camel@localhost.localdomain>
On Wed, 2007-08-29 at 04:31 +1000, Rusty Russell wrote:
> On Mon, 2007-08-27 at 10:16 -0500, Anthony Liguori wrote:
> > @@ -569,6 +570,7 @@ asmlinkage void __init start_kernel(void)
> > }
> > sort_main_extable();
> > trap_init();
> > + kvm_guest_init();
> > rcu_init();
> > init_IRQ();
> > pidhash_init();
>
> Hi Anthony,
>
> This placement seems arbitrary. Why not earlier from setup_arch, or as
> a normal initcall?
The placement is important if we wish to have a paravirt_ops hook for
the interrupt controller. This is the latest possible spot we can do
it. A comment is probably appropriate here.
Regards,
Anthony Liguori
> Rusty.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2007-08-29 5:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 15:16 [PATCH 0/3] KVM paravirtualization framework Anthony Liguori
2007-08-27 15:16 ` [PATCH 1/3] Implement emulator_write_phys() Anthony Liguori
2007-08-27 15:16 ` [PATCH 2/3] Refactor hypercall infrastructure Anthony Liguori
2007-08-27 15:16 ` [PATCH 3/3] KVM paravirt-ops implementation Anthony Liguori
2007-08-28 18:31 ` Rusty Russell
2007-08-29 5:53 ` Anthony Liguori [this message]
2007-08-27 15:16 ` Anthony Liguori
2007-08-27 16:06 ` [PATCH 2/3] Refactor hypercall infrastructure Avi Kivity
2007-08-27 16:06 ` Avi Kivity
2007-08-27 17:29 ` Anthony Liguori
2007-08-27 17:29 ` Anthony Liguori
2007-08-28 18:12 ` Rusty Russell
2007-08-29 5:51 ` [kvm-devel] " Anthony Liguori
2007-08-27 15:45 ` [PATCH 1/3] Implement emulator_write_phys() Avi Kivity
2007-08-27 17:23 ` Anthony Liguori
2007-08-27 17:26 ` Avi Kivity
2007-08-27 17:26 ` Avi Kivity
2007-08-27 17:39 ` Anthony Liguori
2007-08-27 17:47 ` Avi Kivity
2007-08-27 17:47 ` Avi Kivity
2007-08-27 18:09 ` Anthony Liguori
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=1188366795.6337.11.camel@squirrel \
--to=anthony@codemonkey.ws \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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.