[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Don't allow MICROCODE built as a modul


  • To: <caglar@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 17 Oct 2006 20:54:34 +0100
  • Delivery-date: Tue, 17 Oct 2006 13:05:52 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbyJhFTT+poSl4ZEduhtwANk04WTA==
  • Thread-topic: [Xen-devel] [PATCH] Don't allow MICROCODE built as a modul

On 17/10/06 8:10 pm, "S.ÃaÄlar Onur" <caglar@xxxxxxxxxxxxx> wrote:

> Hi;
> 
> Attached patch [against xen-3.0.3-testing.hg]
> fixes "/lib/modules/2.6.12.6-xen/kernel/arch/xen/i386/kernel/microcode.ko
> needs unknown symbol sys_munlock" problem by not allowing microcode as a
> module.

That's not fixing the underlying problem. Why would the microcode driver
require sys_munlock()? I'm sure one of the distros would have provided a
patch already if they were seeing this problem.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.