search for: mfns

Displaying 20 results from an estimated 92 matches for "mfns".

Did you mean: mfn
2013 Jan 28
16
PVH questions
Hello, I''ve had a look at PVH support, and I have a few questions: - events are still dispatched the PV way through the callback, right? - I guess FPU errors don''t trigger an INT13, so I don''t need to handle that? - How about the console and store MFNs from the boot info? Are they still MFNs, or actually PFNs? - How about PV network in non-copy mode? It used to be done with a page transfer, which the frontend would free, does XENMEM_decrease_reservation still use MFNs, or PFNs? Samuel
2012 Jan 21
2
[Ques]:xen_ident_map_ISA ant it's mfns...
Hi, I am bit confused about the do_update_va_mapping call that dom0 makes in xen_ident_map_ISA() to map ffff8800000a0000 to mfn a0. The mfn belongs to DOMID_IO. Before the mfn is mapped, the l1 entry is not empty: 0000000139d08500: 00100001380a0027 After the mapping: 0000000139d08500: 00100000000a0467 as expected. However, the mfn 1380a0 still seems to belong to dom0. Shouldn''t
2012 Sep 08
3
[patch 3/3] xen/privcmd: remove const modifier from declaration
.....58ed953 100644 --- a/include/xen/privcmd.h +++ b/include/xen/privcmd.h @@ -69,7 +69,7 @@ struct privcmd_mmapbatch_v2 { unsigned int num; /* number of pages to populate */ domid_t dom; /* target domain */ __u64 addr; /* virtual address */ - const xen_pfn_t __user *arr; /* array of mfns */ + xen_pfn_t __user *arr; /* array of mfns */ int __user *err; /* array of error codes */ }; diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c index 0ce006a..fceb83e 100644 --- a/drivers/xen/privcmd.c +++ b/drivers/xen/privcmd.c @@ -389,7 +389,7 @@ static long privcmd_ioctl_mmap_ba...
2012 Sep 08
3
[patch 3/3] xen/privcmd: remove const modifier from declaration
.....58ed953 100644 --- a/include/xen/privcmd.h +++ b/include/xen/privcmd.h @@ -69,7 +69,7 @@ struct privcmd_mmapbatch_v2 { unsigned int num; /* number of pages to populate */ domid_t dom; /* target domain */ __u64 addr; /* virtual address */ - const xen_pfn_t __user *arr; /* array of mfns */ + xen_pfn_t __user *arr; /* array of mfns */ int __user *err; /* array of error codes */ }; diff --git a/drivers/xen/privcmd.c b/drivers/xen/privcmd.c index 0ce006a..fceb83e 100644 --- a/drivers/xen/privcmd.c +++ b/drivers/xen/privcmd.c @@ -389,7 +389,7 @@ static long privcmd_ioctl_mmap_ba...
2012 Oct 12
13
Dom0 physical networking/swiotlb/something issue in 3.7-rc1
...following patch causes fairly large packet loss when transmitting from dom0 to the physical network, at least with my tg3 hardware, but I assume it can impact anything which uses this interface. I suspect that the issue is that the compound pages allocated in this way are not backed by contiguous mfns and so things fall apart when the driver tries to do DMA. However I don''t understand why the swiotlb is not fixing this up successfully? The tg3 driver seems to use pci_map_single on this data. Any thoughts? Perhaps the swiotlb (either generically or in the Xen backend) doesn''t c...
2008 Jan 18
0
[PATCH] minios: support COW for a zero page
...f unsigned long *phys_to_machine_mapping; +unsigned long mfn_zero; extern char stack[]; extern void page_walk(unsigned long virt_addr); @@ -492,10 +493,13 @@ static void clear_bootstrap(void) static void clear_bootstrap(void) { struct xen_memory_reservation reservation; - xen_pfn_t mfns[] = { virt_to_mfn(0), virt_to_mfn(&shared_info) }; + xen_pfn_t mfns[] = { virt_to_mfn(&shared_info) }; int n = sizeof(mfns)/sizeof(*mfns); pte_t nullpte = { }; + /* Use page 0 as the CoW zero page */ + memset(NULL, 0, PAGE_SIZE); + mfn_zero = pfn_to_mfn(0); if (...
2010 Mar 10
3
pvSCSI question - can a gref describe more than one page?
Porting the pvSCSI backend driver to the pvops kernel is turning out to be a bit harder than first thought, mostly because all the Linux routines that might be useful are written with the assumption that they would be passed a mapped buffer and they would then build an sg list out of that. pvSCSI already has an sg list, and all the routines that it makes use of have been deprecated since 2.6.18
2008 May 21
6
[PATCH 0/5] xen pvfb: Para-virtual framebuffer, keyboard and pointer driver updates
This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module
2008 May 21
6
[PATCH 0/5] xen pvfb: Para-virtual framebuffer, keyboard and pointer driver updates
This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module
2008 May 21
6
[PATCH 0/5] xen pvfb: Para-virtual framebuffer, keyboard and pointer driver updates
This is an update to the Linux part of the Xen PVFB. Linux Xen PVFB is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. Their backends run in dom0 user space. Parts in this patch series: 1. Enable Xen console by default in domU 2. Pointer z-axis (mouse wheel) support 3. Module
2006 Feb 08
3
[PATCH] direct_remap_pfn_range vm_flags fix
direct_remap_pfn_range() does not properly mark vma with VM_PFNMAP. This triggers improper reference counting on what rmap thought was a normal page, and a subsequent BUG() such as: Eeek! page_mapcount(page) went negative! (-1) page->flags = 414 page->count = 1 page->mapping = 00000000 ------------[ cut here ]------------ kernel BUG at
2007 Mar 26
8
Backend device not found error
Hi, Sometimes when I mount a disk image, unmount it, and then try to create a domU using the disk image I get the following error: Error: Device 2049 (vbd) could not be connected. Backend device not found. Im using a FC4 image. Here is the config file: kernel = "/boot/vmlinuz-2.6.16-rc3-xenU" memory=256 name=Domain1 vif = [''bridge=xenbr0''] disk = [
2008 Dec 19
3
xc_translate_foreign_address() returns mfn??
Hi, I looked at the function xc_translate_foreign_address(), and see that it walks the page table of the guest VM. So at best, it should return the pfn of the guest (?) We can see taht the Later part of the function is like this: ... if (pt_levels >= 3) mfn = (pte & L0_PAGETABLE_MASK_PAE) >> PAGE_SHIFT; else mfn = (pte & L0_PAGETABLE_MASK)
2008 Feb 29
35
[RFC] PVFB: Add refresh period to XenStore parameters?
Hello, Sometimes the backend of PVFB knows that it doesn''t need permanent refresh, when the window is minimized for instance (no refresh at all), or the administration tools know that the window is thumnailed, and so a slow refresh rate is fine. Also, some users may want to tune the refresh rate according to the smoothness they would like, balanced with the CPU time that requires.
2013 Jan 30
2
[PATCH] PVH: remove code to map iomem from guest
...mu.c b/arch/x86/xen/mmu.c index b4be4c9..fbf6a63 100644 --- a/arch/x86/xen/mmu.c +++ b/arch/x86/xen/mmu.c @@ -333,20 +333,6 @@ static void xen_set_pte(pte_t *ptep, pte_t pteval) __xen_set_pte(ptep, pteval); } -void xen_set_clr_mmio_pvh_pte(unsigned long pfn, unsigned long mfn, - int nr_mfns, int add_mapping) -{ - struct physdev_map_iomem iomem; - - iomem.first_gfn = pfn; - iomem.first_mfn = mfn; - iomem.nr_mfns = nr_mfns; - iomem.add_mapping = add_mapping; - - if (HYPERVISOR_physdev_op(PHYSDEVOP_map_iomem, &iomem)) - BUG(); -} - static void xen_set_pte_at(struct mm_struct *mm, u...
2007 Apr 18
1
[rfc][patch][linux] ioctl32() compat plumbing for xen calls
...ntry; -} privcmd_mmap_t; +}; +typedef struct privcmd_mmap privcmd_mmap_t; -typedef struct privcmd_mmapbatch { +struct privcmd_mmapbatch { int num; /* number of pages to populate */ domid_t dom; /* target domain */ __u64 addr; /* virtual address */ xen_pfn_t __user *arr; /* array of mfns - top nibble set on err */ -} privcmd_mmapbatch_t; +}; +typedef struct privcmd_mmapbatch privcmd_mmapbatch_t; + +#ifdef CONFIG_COMPAT +extern int privcmd_ioctl_32(int fd, unsigned int cmd, unsigned long arg); +struct privcmd_mmap_32 { + int num; + domid_t dom; + compat_uptr_t entry; +}; + +struct...
2008 Feb 21
4
[PATCH 0/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer
This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred
2008 Feb 21
4
[PATCH 0/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer
This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred
2008 Feb 21
4
[PATCH 0/2] xen pvfb: Para-virtual framebuffer, keyboard and pointer
This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred
2013 Nov 22
2
Question about the memory layout of xen hypervisor, dom0 and domU
Hi, I have a question about the memory layout of the Xen hypervisor, dom0 and domU. *The goal I want to achieve is: I want to show which RAM area is used by hypervisor, which RAM area is used by dom0, which RAM area is used by each domU (PV guest domain). I hope to know the above information when xen is booted as well as when xen is running some domUs. I already know that we can dedicate a fix