search for: gpfn

Hi, V6: The only change from V5 is in patch #6: - changed comment to reflect autoxlate - removed a redundant ASSERT - reworked logic a bit so that get_page_from_gfn() is called with NULL for p2m type as before. arm has ASSERT wanting it to be NULL. Tim: patch 4 needs your approval. Daniel: patch 5 needs your approval. These patches implement PVH dom0. Patches 1 and 2

Hi, Maybe it''s a dumb question, but I''m actually trying to understand how the memory allocation works within Xen. I try to give 128MB to a domU and see if it increases for example when I "nano" a 500mb file, but the process just get killed when it reachs the 128MB memory limit. How do I configure the guests so they can ask for more memory until a limit is reached

I am using Xen 3.0.4 vmx (on Intel VT). I need to map in a foreign page, given its mfn (not gpfn), into dom0. I used to do this quite well with Xen 3.0.2. However, when I ported my code to Xen 3.0.4, things seem to have changed. Does xc_map_foreign_range accept an mfn or a gpfn as its argument? It seems to be accepting gpfn in 3.0.4. Is that true? If so, can anyone please suggest a way fo...

hi I try to understand the code of xen memory 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...

...r reproducing this one, and this is a reasonably hacked up branch of (domU) XenLinux. So, while I can''t discount bugs in this domU, a domU bug shouldn''t crash Xen like this: (I belive this one was from simply typing halt in domU) (XEN) Assertion ''! IS_INVALID_M2P_ENTRY(gpfn)'' failed, line 395, file shadow32.c(XEN) BUG at shadow32.c:395 (XEN) ----[ Xen-3.0-unstable Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: e008:[<ff14ad8d>] free_shadow_page+0xd5/0x2ef (XEN) EFLAGS: 00010282 CONTEXT: hypervisor (XEN) eax: ff1a9818 ebx: ffffffff ecx: 00002a0...

Keir Fraser wrote: > On 29 Mar 2006, at 17:09, Nakajima, Jun wrote: > >> Are you doing live migration? In the default setup for domUs, the >> shadow code is never used. > > The mini patches for Linux we submitted to lkml depend on shadow mode. > > -- Keir > So this is _not_ for 3.0.2? I expect some hiccups with that if domUs start using other than log-dirty

...m/platform.h> +#endif struct memop_args { /* INPUT */ @@ -90,7 +93,7 @@ static void increase_reservation(struct memop_args *a) static void populate_physmap(struct memop_args *a) { - struct page_info *page; + struct page_info *page = NULL; unsigned long i, j; xen_pfn_t gpfn, mfn; struct domain *d = a->domain; @@ -122,7 +125,33 @@ static void populate_physmap(struct memop_args *a) } else { - page = alloc_domheap_pages(d, a->extent_order, a->memflags); +#ifdef CONFIG_ARM + if ( d == dom0 && platform_...

...static int map_foreign_page(unsigned long lpfn, unsigned long fgmfn, + unsigned int domid) +{ + int rc; + struct xen_add_to_physmap_range xatp = { + .domid = DOMID_SELF, + .foreign_domid = domid, + .size = 1, + .space = XENMAPSPACE_gmfn_foreign, + }; + xen_ulong_t idx = fgmfn; + xen_pfn_t gpfn = lpfn; + + set_xen_guest_handle(xatp.idxs, &idx); + set_xen_guest_handle(xatp.gpfns, &gpfn); + + rc = HYPERVISOR_memory_op(XENMEM_add_to_physmap_range, &xatp); + if (rc) { + pr_warn("Failed to map pfn to mfn rc:%d pfn:%lx mfn:%lx\n", + rc, lpfn, fgmfn); + return 1; + } +...

...i = a->nr_done; i < a->nr_extents; i++ ) @@ -115,8 +116,7 @@ static void populate_physmap(struct memo if ( a->memflags & MEMF_populate_on_demand ) { - if ( a->extent_order > MAX_ORDER || - guest_physmap_mark_populate_on_demand(d, gpfn, + if ( guest_physmap_mark_populate_on_demand(d, gpfn, a->extent_order) < 0 ) goto out; } _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lis...

A number of build problems crept in once again. Fix them. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/common/memory.c +++ b/xen/common/memory.c @@ -683,7 +683,7 @@ long do_memory_op(unsigned long cmd, XEN mfn = get_gfn_untyped(d, xrfp.gpfn); if ( mfn_valid(mfn) ) - guest_physmap_remove_page(d, xrfp.gpfn, mfn, PAGE_ORDER_4K); + guest_physmap_remove_page(d, xrfp.gpfn, mfn, 0); else rc = -ENOENT; --- a/xen/include/asm-ia64/linux-xen/asm/irq.h +++ b/xen/include/asm-ia64/linux-xen/a...

I have a 12GB 64-bit Linux HVM guest (CentOS 5.5). When I look at the e820 map in the guest, I see the following: BIOS-provided physical RAM map: BIOS-e820: 0000000000010000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000f0000000 (usable) BIOS-e820:

...unlock(p2m); > return 0; > out_of_memory: > diff --git a/xen/include/asm-x86/p2m.h b/xen/include/asm-x86/p2m.h > --- a/xen/include/asm-x86/p2m.h > +++ b/xen/include/asm-x86/p2m.h > @@ -287,6 +287,10 @@ struct p2m_domain { > unsigned reclaim_super; /* Last gpfn of a scan */ > unsigned reclaim_single; /* Last gpfn of a scan */ > unsigned max_guest; /* gpfn of max guest > demand-populate */ > +#define POD_HISTORY_MAX 128 > + /* gpfn of last guest superpage demand-populated */ > + unsigned...

...hows the address range 0000000c14000000->0000000c18000000 , what is this? it''s 64MB range and why 64MB from Dom0 is located here? I think 498514 pages will be allocated later, but where, exactly?? if dom0''s memory is partitioned into several places, then, what happens to their GPFN?? thanks Min

This series implements ballooning for Xen on ARM and builds and Mukesh''s PVH privcmd stuff to implement foreign page mapping on ARM, replacing the old "HACK: initial (very hacky) XENMAPSPACE_gmfn_foreign" patch. The baseline is a bit complex, it is basically Stefano''s xenarm-forlinus branch (commit bbd6eb29214e) merged with Konrad''s linux-next-pvh branch

Hi Jeremy. Here are the 3 patches for ia64/xen support. The first one is just to move manage.c under drivers/xen. This is trivial. The second and third ones are for compilation fix on ia64. You may want to postpone those 2 patches to make your merge task easy as you said before. thanks, Diffstat arch/x86/xen/Makefile | 2 +- drivers/xen/Makefile | 2 +-

Hi Jeremy. Here are the 3 patches for ia64/xen support. The first one is just to move manage.c under drivers/xen. This is trivial. The second and third ones are for compilation fix on ia64. You may want to postpone those 2 patches to make your merge task easy as you said before. thanks, Diffstat arch/x86/xen/Makefile | 2 +- drivers/xen/Makefile | 2 +-

Hello, I''m new to Xen and especially to the hypervisor code. I''m working off a 3.0.4.1 base and have the following questions regarding the memory management code for an x86, 32-bit platform (capable of supporting PAE). I''m doing some research into providing grant table hypercall support from a Windows 2003 HVM. I have made all the necessary changes to allow the

...tually being checked? [yes, I have read the code, but I confess I don''t understand enough about the internal workings of the shadow page-table to know what''s going on in this bit of code]. The code is based on XenSource changeset 8677:b721455c5e44. -- Mats (XEN) d->id=1 gpfn=0 gmfn=567a7 stype=a0000000 c=80000004 t=00000000f0000002 mfn_out_of_sync(gmfn)=0 mfn_is_page_table(gmfn)=0 (XEN) BUG at /root/xen-unstable-x64.hg/xen/include/asm/shadow.h:1222 (XEN) CPU: 0 (XEN) RIP: e010:[<ffff830000185ab8>] (XEN) RFLAGS: 0000000000010286 CONTEXT: hypervisor (XEN)...

...-990,6 +992,8 @@ static int xenmem_add_to_physmap_one( if ( idx < nr_grant_frames(d->grant_table) ) mfn = virt_to_mfn(d->grant_table->shared_raw[idx]); + else + return -EINVAL; } d->arch.grant_table_gpfn[idx] = gpfn; @@ -999,6 +1003,8 @@ static int xenmem_add_to_physmap_one( case XENMAPSPACE_shared_info: if ( idx == 0 ) mfn = virt_to_mfn(d->shared_info); + else + return -EINVAL; break; case XENMAPSPACE_gmfn_foreign: { -- 1.8.3.1

...+ { + struct page_info *page; + /* alloc a new page to compensate the pod list */ + page = alloc_domheap_page(d, 0); + if ( unlikely(page == NULL) ) + { + goto out_entry_check; + } + set_p2m_entry(d, gpfn + i, _mfn(INVALID_MFN), 0, p2m_invalid); + p2m_mem_paging_drop_page(d, gpfn+i); + p2m_pod_cache_add(d, page, 0); + steal_for_cache = ( p2md->pod.entry_count > p2md->pod.count ); + nonpod--; + ram--; + } + /* for other ra...