Xen devel - Apr 2007 - Correct the wrong setting to EFLAGS in hvm_mmio_assist()

The attached patch corrects the wrong setting to EFLAGS in
hvm_mmio_assist().

Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>


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

Sorry, I forgot to add a "[Patch]" in the subject of the mail.

Btw, can we replace the local variable "diff" in hvm_mmio_assist()
with "result"?.

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Cui, Dexuan
Sent: 2007年4月5日 15:17
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] Correct the wrong setting to EFLAGS in hvm_mmio_assist()

The attached patch corrects the wrong setting to EFLAGS in
hvm_mmio_assist().

Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>

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

hi
I try to understand the code of xen memory ,and I am confused  about  
the  memory-management modes,could someone help me

there are gmfn, gpfn and pfn  in the xen ,and in the 
/xen/include/xen/mm.h  there are some explanation about them as follows:

* 1. gpfn/gpaddr: A guest-specific pseudo-physical frame number or address.
* 2. gmfn/gmaddr: A machine address from the p.o.v. of a particular guest.
* 3. mfn/maddr:   A real machine frame number or address.
* 4. pfn/paddr:   Used in ''polymorphic'' functions that work
across all
*                 address spaces, depending on context. See the pagetable
*                 conversion macros in asm-x86/page.h for examples.
*                 Also ''paddr_t'' is big enough to store any
physical
address.
*

I seems to understand the meaning about them,but I am confused about  
the different memory-management modes as follows

* This scheme provides consistent function and variable names even when
* different guests are running in different memory-management modes.
* 1. A guest running in auto-translated mode (e.g., 
shadow_mode_translate())
*    will have gpfn == gmfn and gmfn != mfn.
* 2. A paravirtualised x86 guest will have gpfn != gmfn and gmfn == mfn.
* 3. A paravirtualised guest with no pseudophysical overlay will have
*    gpfn == gpmfn == mfn.
*

what is the meaning about auto-translated mode,is it not the same with 
paravirtualised one ?
does the auto-translated mode work for hvm and shadow mode? how does it 
work?
and what is the mechanism about paravirtualised guest with no 
pseudophysical overlay?

I am confused about it

could you help me
Thanks in advance

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

hi
 I try to understand the code of xen memory ,and I am confused  about  
gmfn, gpfn and pfn  in the xen
 and in the /xen/include/xen/mm.h  there are some explanation about them 
as follows:

* 1. gpfn/gpaddr: A guest-specific pseudo-physical frame number or address.
* 2. gmfn/gmaddr: A machine address from the p.o.v. of a particular guest.
* 3. mfn/maddr:   A real machine frame number or address.
* 4. pfn/paddr:   Used in ''polymorphic'' functions that work
across all
*                 address spaces, depending on context. See the pagetable
*                 conversion macros in asm-x86/page.h for examples.
*                 Also ''paddr_t'' is big enough to store any
physical
address.
*

last week,I thought I understood the meaning about the gpfn and gmfn,but 
when I  reread  it ,I  find  I do not
I usually think the gpfn/gpaddr is just the gmfn ,that is, 
guest-specific pseudo-physical frame number is just machine address from 
the p.o.v. of a particular guest

I am confused about why does guest-specific pseudo-physical frame 
number  not  equal to machine address from the p.o.v. of a particular guest?

could you help me
Thanks in advance


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