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

Re: [Xen-devel] shadow_fault()

  • To: hyj <hyjshanghai@xxxxxxxxxxx>
  • From: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Mon, 25 Feb 2008 09:43:18 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 26 Feb 2008 03:31:01 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=aYVwVHxPxmrc2apOkC57z7ZOwuvXaBv4DmKyiWJhsl5VxiekO2tr4QYormKtKquV1lCwqQT2I8PP/pbaOckQ88z7g+oX6ykoqvdhBDwQ1cWiNYp4UE1IedvsUWBEild+qwAH81OgSjFaWIFhSakevsypv7phHeZvMF3DAh5/BfM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm afraid the code itself, with inline comments, is always going to
be the most up-to-date and accurate documentation.  The code itself is
constantly changing (usually becoming more complex, unfortunately).
Every time I work with the code again, I usually  need to spend some
time re-familiarizing myself with it.  I find it doubtful that if such
a document existed, it would be significantly less complex than the
code itself.

Perhaps you could start with a specific question (i.e., why does
sh_page_fault() do X?) or a specific goal you're trying to accomplish?


On Mon, Feb 25, 2008 at 8:05 AM, hyj <hyjshanghai@xxxxxxxxxxx> wrote:
> Hi, everyone:
>          I studying how Xen deals with shadow page fault. The code of
> shadow_fault() and its calling functions is too complex. I would be grateful
> if you can give me some detailed documentation on Xen's shadow page fault
> handling mechanism.
>          Thanks!
> Best wishes,
> Kikanjuu
> _______________________________________________
>  Xen-devel mailing list
>  Xen-devel@xxxxxxxxxxxxxxxxxxx
>  http://lists.xensource.com/xen-devel

Xen-devel mailing list



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