search for: mem_init

...it(void) > +{ > + if (!sev_active()) can't you just use is_prot_virt_guest here? > + return; > + > + /* make sure bounce buffers are shared */ > + swiotlb_init(1); > + swiotlb_update_mem_attributes(); > + swiotlb_force = SWIOTLB_FORCE; > +} > + > void __init mem_init(void) > { > cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); > @@ -134,6 +182,8 @@ void __init mem_init(void) > set_max_mapnr(max_low_pfn); > high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); > > + pv_init(); > + > /* Setup guest page hintin...

...it(void) > +{ > + if (!sev_active()) can't you just use is_prot_virt_guest here? > + return; > + > + /* make sure bounce buffers are shared */ > + swiotlb_init(1); > + swiotlb_update_mem_attributes(); > + swiotlb_force = SWIOTLB_FORCE; > +} > + > void __init mem_init(void) > { > cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); > @@ -134,6 +182,8 @@ void __init mem_init(void) > set_max_mapnr(max_low_pfn); > high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); > > + pv_init(); > + > /* Setup guest page hintin...

...-#define __SH_KMAP_TYPES_H - -/* Dummy header just to define km_type. */ - -#ifdef CONFIG_DEBUG_HIGHMEM -#define __WITH_KM_FENCE -#endif - -#include <asm-generic/kmap_types.h> - -#undef __WITH_KM_FENCE - -#endif --- a/arch/sh/mm/init.c +++ b/arch/sh/mm/init.c @@ -362,9 +362,6 @@ void __init mem_init(void) mem_init_print_info(NULL); pr_info("virtual kernel memory layout:\n" " fixmap : 0x%08lx - 0x%08lx (%4ld kB)\n" -#ifdef CONFIG_HIGHMEM - " pkmap : 0x%08lx - 0x%08lx (%4ld kB)\n" -#endif " vmalloc : 0x%08lx - 0x%08lx (%4ld MB)\n&qu...

...rotected virtualization */ > +static void pv_init(void) > +{ > + if (!sev_active()) > + return; > + > + /* make sure bounce buffers are shared */ > + swiotlb_init(1); > + swiotlb_update_mem_attributes(); > + swiotlb_force = SWIOTLB_FORCE; > +} > + > void __init mem_init(void) > { > cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); > @@ -134,6 +176,8 @@ void __init mem_init(void) > set_max_mapnr(max_low_pfn); > high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); > > + pv_init(); > + > /* Setup guest page hintin...

...ttr > __change_page_attr_set_clr > __set_memory_enc_dec > set_memory_decrypted > sev_es_init_ghcbs > trap_init -> before mm_init (in init/main.c) > start_kernel > x86_64_start_reservations > x86_64_start_kernel > secondary_startup_64 > > At this time, mem_init hasn't been called yet (which would be called by > mm_init). Thus, the free pages are still owned by memblock. It's in mem_init > (x86/mm/init_64.c) that memblock_free_all gets called and free pages are > released. > > During testing, I've also noticed that debug_pageall...

Running with Xen option dom0_mem=6G and kernel option mem=8G, I would have expected that I would see the system with a 2G balloon right after boot. However, the balloon is empty. Briefly looking at this, it would seem to me that, with all pages being reserved when the system starts and only the populated ones getting the reserved status cleared in __free_pages_bootmem(), the condition to put pages

...rot_virt_guest(); +} +EXPORT_SYMBOL_GPL(sev_active); + +/* protected virtualization */ +static void pv_init(void) +{ + if (!sev_active()) + return; + + /* make sure bounce buffers are shared */ + swiotlb_init(1); + swiotlb_update_mem_attributes(); + swiotlb_force = SWIOTLB_FORCE; +} + void __init mem_init(void) { cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); @@ -134,6 +182,8 @@ void __init mem_init(void) set_max_mapnr(max_low_pfn); high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); + pv_init(); + /* Setup guest page hinting */ cmma_init(); -- 2.16.4

...e(void) +{ + return is_prot_virt_guest(); +} + +/* protected virtualization */ +static void pv_init(void) +{ + if (!is_prot_virt_guest()) + return; + + /* make sure bounce buffers are shared */ + swiotlb_init(1); + swiotlb_update_mem_attributes(); + swiotlb_force = SWIOTLB_FORCE; +} + void __init mem_init(void) { cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); @@ -136,6 +181,8 @@ void __init mem_init(void) set_max_mapnr(max_low_pfn); high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); + pv_init(); + /* Setup guest page hinting */ cmma_init(); -- 2.17.1

...e(void) +{ + return is_prot_virt_guest(); +} + +/* protected virtualization */ +static void pv_init(void) +{ + if (!is_prot_virt_guest()) + return; + + /* make sure bounce buffers are shared */ + swiotlb_init(1); + swiotlb_update_mem_attributes(); + swiotlb_force = SWIOTLB_FORCE; +} + void __init mem_init(void) { cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); @@ -136,6 +181,8 @@ void __init mem_init(void) set_max_mapnr(max_low_pfn); high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); + pv_init(); + /* Setup guest page hinting */ cmma_init(); -- 2.17.1

...cc/__ashldi3.o libgcc/__udivdi3.o \ libgcc/__negdi2.o libgcc/__ashrdi3.o libgcc/__lshrdi3.o \ diff --git a/core/extern.inc b/core/extern.inc index 3cde286..953be42 100644 --- a/core/extern.inc +++ b/core/extern.inc @@ -27,8 +27,6 @@ extern hexdump, mydump - extern printf_init - extern mem_init ; fs.c diff --git a/core/hello.c b/core/hello.c index d30fc3b..bed7cb5 100644 --- a/core/hello.c +++ b/core/hello.c @@ -76,8 +76,3 @@ void mp5(void) myprint(5); } -void printf_init(void) -{ - openconsole(&dev_null_r, &dev_stdcon_w); -} - diff --git a/core/init.c b/core/init.c index...

...e(void) +{ + return is_prot_virt_guest(); +} + +/* protected virtualization */ +static void pv_init(void) +{ + if (!is_prot_virt_guest()) + return; + + /* make sure bounce buffers are shared */ + swiotlb_init(1); + swiotlb_update_mem_attributes(); + swiotlb_force = SWIOTLB_FORCE; +} + void __init mem_init(void) { cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); @@ -136,6 +181,8 @@ void __init mem_init(void) set_max_mapnr(max_low_pfn); high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); + pv_init(); + /* Setup guest page hinting */ cmma_init(); -- 2.13.4

...e(void) +{ + return is_prot_virt_guest(); +} + +/* protected virtualization */ +static void pv_init(void) +{ + if (!is_prot_virt_guest()) + return; + + /* make sure bounce buffers are shared */ + swiotlb_init(1); + swiotlb_update_mem_attributes(); + swiotlb_force = SWIOTLB_FORCE; +} + void __init mem_init(void) { cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); @@ -136,6 +181,8 @@ void __init mem_init(void) set_max_mapnr(max_low_pfn); high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); + pv_init(); + /* Setup guest page hinting */ cmma_init(); -- 2.13.4

Hi all, a newbie question. I''m trying to install lenny guest image (in an img file) on my lenny Dom0 by following the http://wiki.debian.org/Xen: xm create -c xm-debian.cfg install=true install-mirror=ftp://ftp.XX.debian.org/debian i created the xen-lenny-image.img using dd, format is ext3. disk is defined as (cfg file): disk =

...)) > > > + return; > > > + > > > + /* make sure bounce buffers are shared */ > > > + swiotlb_init(1); > > > + swiotlb_update_mem_attributes(); > > > + swiotlb_force = SWIOTLB_FORCE; > > > +} > > > + > > > void __init mem_init(void) > > > { > > > cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); > > > @@ -134,6 +176,8 @@ void __init mem_init(void) > > > set_max_mapnr(max_low_pfn); > > > high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); > > >...

...ending code snippet from sysutils/wmmemmon's mem_freebsd.c file: -------------------------------------------------------------- static kvm_t *kvm_data = NULL; static int pageshift; static struct nlist nlst[] = { {"_cp_time"}, {"_cnt"}, {0} }; /* initialize function */ void mem_init(void) { int pagesize = getpagesize(); pageshift = 0; while (pagesize > 1) { pageshift++; pagesize >>= 1; } kvm_data = kvm_open(NULL, NULL, NULL, O_RDONLY, "kvm_open"); if (kvm_data == NULL) { fprintf(stderr, "can't open kernel...

...ketchy to nice. Thanks again! Regards, Halil > > + return; > > + > > + /* make sure bounce buffers are shared */ > > + swiotlb_init(1); > > + swiotlb_update_mem_attributes(); > > + swiotlb_force = SWIOTLB_FORCE; > > +} > > + > > void __init mem_init(void) > > { > > cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); > > @@ -134,6 +182,8 @@ void __init mem_init(void) > > set_max_mapnr(max_low_pfn); > > high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); > > > > + pv_init(); >...

...n */ > +static void pv_init(void) > +{ > +??? if (!sev_active()) > +??????? return; > + > +??? /* make sure bounce buffers are shared */ > +??? swiotlb_init(1); > +??? swiotlb_update_mem_attributes(); > +??? swiotlb_force = SWIOTLB_FORCE; > +} > + > ?void __init mem_init(void) > ?{ > ???? cpumask_set_cpu(0, &init_mm.context.cpu_attach_mask); > @@ -134,6 +182,8 @@ void __init mem_init(void) > ???? set_max_mapnr(max_low_pfn); > ???????? high_memory = (void *) __va(max_low_pfn * PAGE_SIZE); > ?+??? pv_init(); > + > ???? /* Setup guest...

....after_bootmem = paravirt_nop, > }; > > struct pv_time_ops pv_time_ops = { > diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c > index 79cb066f40c0..6096d0d9ecbc 100644 > --- a/arch/x86/mm/init_32.c > +++ b/arch/x86/mm/init_32.c > @@ -763,6 +763,7 @@ void __init mem_init(void) > free_all_bootmem(); > > after_bootmem = 1; > + paravirt_after_bootmem(); > > mem_init_print_info(NULL); > printk(KERN_INFO "virtual kernel memory layout:\n" > diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c > index 332f6e25977a..70...

...d_dmar+0x7f/0xa0 :[<c04551d3>] ? warn_slowpath_fmt_taint+0x33/0x40 :[<c06217ff>] ? warn_invalid_dmar+0x7f/0xa0 :[<c0abdeb8>] ? check_zero_address+0xfb/0x132 :[<c06608b7>] ? acpi_tb_verify_table+0x1d/0x46 :[<c0abdefd>] ? detect_intel_iommu+0xe/0x57 :[<c0aae15b>] ? mem_init+0x10/0x2ab :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.clone.0+0x87/0xa1 :[<c0828e00>] ? rcu_init_percpu_data.c...

...> > */ > > mem_encrypt_init(); > > > > So, I'm wondering if creating the console device interacts in any way > > with the memory encryption interface? > > I do things a bit different than x86: the SWIOTLB stuff is set up in > mem_init(). So I think we should be fine. If there is a down-side to > calling swiotlb_update_mem_attributes() earlier, honestly I'm > not sure. Neither am I; do any of the folks who looked at the swiotlb patch have an idea? > > > > > [Does basic recognition work if you start a...