WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Drivers

To: "Charles Coffing" <ccoffing@xxxxxxxxxx>
Subject: Re: [Xen-devel] Drivers
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 25 Oct 2004 23:50:47 +0100
Cc: Ian.Pratt@xxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxxx, "Ky Srinivasan" <KSrinivasan.PRV-5.PROVO@xxxxxxxxxx>, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 26 Oct 2004 01:41:57 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Mon, 25 Oct 2004 15:42:12 MDT." <s17d1edc.072@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> Related to this, I wrote a little script that disassembles the kernel
> and drivers, looking for privileged instructions.  (The BUG macro must
> first be modified to avoid many false positives, however.) 

That's certainly a useful exercise. 
  
> It turned up a problem in the file
> linux-2.6.8.1/drivers/mtd/maps/nettel.c.  I've attached a patch -- can
> we put this in the patches directory? 

Definitely -- remind me if it doesn't appear soon.

> I also noticed a number of scary things in the kernel itself (moves
> to/from CR4, various CLI/STI pairs, maybe some others but I forget ATM)
> but it appears that these are avoided at runtime.  Some of these could
> and probably should be cleaned up, though, since they exist in the
> arch/xen tree.  I'll come back with some more details on this. 

Because of the 'minimum changes' approach we've taken to the 2.6
port there's a certain amount of code that's compiled in but
never used. Hopefully these instructions will be on those paths,
but it would be nice to have a list of them to verify.
If/when we're in the mainstream kernel tree we can take a more
aggressive approach about cleaning things up.

Ian


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>