[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1175743584.9371.47.camel@localhost.localdomain>
Date: Wed, 04 Apr 2007 23:26:24 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: virtualization@...ts.osdl.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Glauber de Oliveira Costa <glommer@...il.com>
Subject: Re: [PATCH] Lguest32, use guest page tables to find paddr for
emulated instructions
On Thu, 2007-04-05 at 12:59 +1000, Rusty Russell wrote:
> On Wed, 2007-04-04 at 15:07 -0400, Steven Rostedt wrote:
> Yeah, I haven't tried loading random modules but I can imagine this does
> happen (what module was it, BTW?)
I have no idea of which module it crashed on. I didn't investigate that
too much. I could simply send a trap to guest when
__pa(addr) != lguest_find_guest_paddr(addr) and see which module it
crashed on.
My block device I used was basically a copy of a RHEL5 system. I only
modified the inittab and fstab to get it working. So on startup and
doing the udev init was when it crashed.
>
> I used to have a function just like this, but managed to get rid of
> it.
>
> Hmm, perhaps we should have an "int lgread_virt_byte(u8 *)" which does
> the pgtable walk and read all in one? It won't be efficient, but it'll
> be more correct and maybe even fewer lines 8)
I forgot that you have a goal to keep lguest small :)
Perhaps we can fork, and have lguest and lguest-lite.
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists