Re: [Xen-devel] [RFC PATCH 00/19] xen/arm: Add ITS support

Hi Julien, On Mon, Mar 9, 2015 at 11:46 PM, Julien Grall wrote: > Hello Vijay, > > On 09/03/2015 14:57, Vijay Kilari wrote: >> >> On Tue, Mar 3, 2015 at 5:13 PM, Julien Grall >> wrote: >>> >>> Hello Vijay, >>> >>> On 03/03/2015 03:55, Vijay Kilari wrote: On Mon, Mar 2, 2015 at 6:4

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

>>> On 3/12/2015 at 06:21 PM, in message , wrote: > Hi all > > We are now two months into 4.6 development window. This is an email to keep > track of all the patch series I gathered. It is by no means complete and / > or > acurate. Feel free to reply this email with new projects or corre

Re: [Xen-devel] [PATCH v6 04/30] xen/PCI: Don't use deprecated function pci_scan_bus_parented()

+ pci_add_resource(&resources, &ioport_resource); + pci_add_resource(&resources, &iomem_resource); + pci_add_resource(&resources, &busn_resource); >>> >>> Since I don't want to export busn_resource, you might have to allocate your >>> own struct resource for it here. And, of cour

Re: [Xen-devel] [v2][PATCH 2/2] libxl: introduce gfx_passthru_kind

I don't think you can abort here, since a user can set b_info->u.hvm.gfx_passthru_kind to default. You would need to return an error. Then, looks I should do this, LOG(ERROR, "No supported IGD to passthru," " or please force set gfx_passthru=\"igd\".\

Re: [Xen-devel] [PATCHv5 12/14] xen-blkback: safely unmap grants in case they are still in use

On 03/13/2015 02:25 AM, David Vrabel wrote: > On 12/03/15 03:30, Roger Pau Monné wrote: >> >> @@ -343,20 +353,19 @@ void xen_blkbk_unmap_purged_grants(struct work_struct >> *work) >> >> pages[segs_to_unmap] = persistent_gnt->page; >> >> -if (++segs_to_unmap == BLKIF_M

Re: [Xen-devel] [PATCH 2/3] libsepol, checkpolicy: widen Xen IOMEM ocontext entries

On 12/03/2015 20:40, Daniel De Graaf wrote: > This expands IOMEMCON device context entries to 64 bits. This change is > required to support static I/O memory range labeling for systems with > over 16TB of physical address space. The policy version number change > is shared with the next patch. >

Re: [Xen-devel] xenstored crashes with SIGSEGV

Hello, On 12.03.2015 19:17, Oleg Nesterov wrote: > On 03/12, Philipp Hahn wrote: >> >> Have you seen any other corruption > > No, > >> or is one of your patches likely to >> fix something like the issue mentioned above: > > I am not sure I even understand the problem above ;) I mean, after the q

Re: [Xen-devel] [PATCH 1/2] iommu VT-d: separate rmrr addition function

- elena.ufimts...@oracle.com wrote: > On Wed, Mar 11, 2015 at 10:29:54AM +, Jan Beulich wrote: > > >>> On 09.03.15 at 15:42, wrote: > > > --- a/xen/drivers/passthrough/vtd/dmar.c > > > +++ b/xen/drivers/passthrough/vtd/dmar.c > > > @@ -567,6 +567,66 @@ out: > > > return ret; > > >

Re: [Xen-devel] [PATCH] VHD: Fix locale aware character encoding handling

Hello Ian, On 11.03.2015 13:30, Ian Campbell wrote: > On Sun, 2015-03-08 at 11:54 +0100, Philipp Hahn wrote: >> ASCII is 7 bit only, which does not work in UTF-8 environments: >>> failed to read parent name ... >> Don't check outbytesleft==0 as one UTF-8 characters get encoded into >> 1..8 bytes,

Re: [Xen-devel] [PATCH 2/2] iommu: add rmrr Xen command line option for misc rmrrs

On Mon, Mar 09, 2015 at 05:16:18PM +, Andrew Cooper wrote: > On 09/03/15 14:42, elena.ufimts...@oracle.com wrote: > > From: Elena Ufimtseva > > > > On some platforms RMRR regions may be not specified > > in ACPI and thus will not be mapped 1:1 in dom0. This > > causes IO Page Faults and preven

Re: [Xen-devel] [PATCH 1/2] iommu VT-d: separate rmrr addition function

On Wed, Mar 11, 2015 at 10:29:54AM +, Jan Beulich wrote: > >>> On 09.03.15 at 15:42, wrote: > > --- a/xen/drivers/passthrough/vtd/dmar.c > > +++ b/xen/drivers/passthrough/vtd/dmar.c > > @@ -567,6 +567,66 @@ out: > > return ret; > > } > > > > +int register_one_rmrr(struct acpi_rmrr_unit

[Xen-devel] [PATCH 3/3] libsepol, checkpolicy: add device tree ocontext nodes to Xen policy

In Xen on ARM, device tree nodes identified by a path (string) need to be labeled by the security policy. Signed-off-by: Daniel De Graaf --- checkpolicy/policy_define.c| 55 + checkpolicy/policy_define.h| 1 + checkpolicy/policy_parse.y

[Xen-devel] [PATCH v2 0/3] Xen/FLASK policy updates for device contexts

In order to support assigning security lables to ARM device tree nodes in Xen's XSM policy, a new ocontext type is needed in the security policy. In addition to adding the new ocontext, the existing I/O memory range ocontext is expanded to 64 bits in order to support hardware with more than 44 bit

[Xen-devel] [PATCH 2/3] libsepol, checkpolicy: widen Xen IOMEM ocontext entries

This expands IOMEMCON device context entries to 64 bits. This change is required to support static I/O memory range labeling for systems with over 16TB of physical address space. The policy version number change is shared with the next patch. While this makes no changes to SELinux policy, a new

[Xen-devel] [PATCH v2] xsm: add device tree labeling support

This adds support in the hypervisor and policy build toolchain for Xen/Flask policy version 30, which adds the ability to label ARM device tree nodes and expands the IOMEM ocontext entries to 64 bits. Signed-off-by: Daniel De Graaf --- tools/flask/policy/Makefile | 20 -- xen/include/

[Xen-devel] [PATCH 1/3] checkpolicy: Expand allowed character set in paths

In order to support paths containing spaces or other characters, allow a quoted string with these characters to be parsed as a path in addition to the existing unquoted string. Signed-off-by: Daniel De Graaf --- checkpolicy/policy_parse.y | 3 +++ checkpolicy/policy_scan.l | 1 + 2 files change

Re: [Xen-devel] [PATCH v6 04/30] xen/PCI: Don't use deprecated function pci_scan_bus_parented()

On Thu, Mar 12, 2015 at 07:46:45PM +0800, Yijing Wang wrote: > >>struct pci_bus *b; > >> + LIST_HEAD(resources); > >>struct pcifront_sd *sd = NULL; > >>struct pci_bus_entry *bus_entry = NULL; > >>int err = 0; > >> @@ -470,17 +472,21 @@ static int pcifront_scan_root(struct pcifront_

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

2015-03-12 11:39 GMT-04:00 Dario Faggioli : > > On Thu, 2015-03-12 at 15:07 +, Ian Campbell wrote: > > On Thu, 2015-03-12 at 10:21 +, wei.l...@citrix.com wrote: > > > > > * Repurpose SEDF Scheduler for Real-time (fair) > > >RFC patch posted (v2) > > > - Joshua Whitehead, Robert VanV

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

On Thu, Mar 12, 2015 at 10:21:56AM +, wei.l...@citrix.com wrote: [...] > == GRUB2 == > > * GRUB2 multiboot2 (fair) > - Daniel Kiper RFC patches were posted (see: http://lists.xen.org/archives/html/xen-devel/2015-01/msg03982.html). Weeding out bugs found during testing. I am going to pos

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

>-Original Message- >From: wei.l...@citrix.com [mailto:wei.l...@citrix.com] > >* extending mem_access support to PV domain (fair) > RFC v2 > - Aravindh Puthiyaparambil (aravindp) We did some internal reprioritizing and decided to focus on HVM and PVH domains. This can be placed in de

Re: [Xen-devel] Xen-unstable: "root=" no longer prepended on kernel cmdline since commit "tools: xl: handle unspecified extra= when dealing with root="

Thursday, March 12, 2015, 6:59:06 PM, you wrote: > On Thu, 2015-03-12 at 18:48 +0100, Sander Eikelenboom wrote: >> Hi Ian, >> >> My PV-guest configs were still using the old "root=" option, >> but these guests don't boot anymore since: >> commit 49ab17a3a615e1ab4ccc46d6942f925cf841df4b, >> "tool

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

On Thu, Mar 12, 2015 at 03:07:33PM +, Ian Campbell wrote: > On Thu, 2015-03-12 at 10:21 +, wei.l...@citrix.com wrote: [...] > > * Rearrange and cleanup installation destination directories (/var -> > > var/lib/xen) (fair) > > - Daniel Kiper > > What is this? I've never heard about it

Re: [Xen-devel] [PATCHv5 12/14] xen-blkback: safely unmap grants in case they are still in use

On 12/03/15 03:30, Roger Pau Monné wrote: > > @@ -343,20 +353,19 @@ void xen_blkbk_unmap_purged_grants(struct work_struct > *work) > > pages[segs_to_unmap] = persistent_gnt->page; > > - if (++segs_to_unmap == BLKIF_MAX_SEGMENTS_PER_REQUEST) { > -

Re: [Xen-devel] xenstored crashes with SIGSEGV

On 03/12, Philipp Hahn wrote: > > Have you seen any other corruption No, > or is one of your patches likely to > fix something like the issue mentioned above: I am not sure I even understand the problem above ;) I mean, after the quick look I do not see how this connects to FPU. $rdi == 2 looks

Re: [Xen-devel] [PATCH] xsm: add device tree labeling support

Hi Daniel, On 12/03/15 17:13, Daniel De Graaf wrote: > int security_find_bool(const char *name) > { > int i, rv = -ENOENT; > @@ -2131,7 +2166,7 @@ int security_ocontext_add( u32 ocon, unsigned long low, > unsigned long high > c->u.iomem.high_iomem == high && c->sid[0] == s

Re: [Xen-devel] [PATCH v7] sndif: add ABI for Para-virtual sound

> On 23 Feb 2015, at 17:41, Ian Campbell wrote: > > On Fri, 2015-02-06 at 13:28 +0200, Oleksandr Dmytryshyn wrote: >> This is ABI for the two halves of a Para-virtual >> sound driver to communicate with each to other. >> >> Signed-off-by: Oleksandr Dmytryshyn >> Signed-off-by: Iurii Konovalenk

Re: [Xen-devel] [PATCH] xsm: add device tree labeling support

Hi Daniel, On 12/03/15 17:13, Daniel De Graaf wrote: > This adds support in the hypervisor and policy build toolchain for > Xen/Flask policy version 25, which adds the ability to label ARM device > tree nodes and expands the IOMEM ocontext entries to 64 bits. > > Signed-off-by: Daniel De Graaf >

[Xen-devel] [Mini-os] Fix accidentally removed brace causing a build error.

Introduced in: commit bd5920cb92e6799bfd64957284a9e2cfe7699039 "mini-os: sort objects in binary archives" Signed-off-by: Sander Eikelenboom --- Makefile |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 3e5d95e..2cb5e51 100644 --- a/Makefile +++ b/M

Re: [Xen-devel] [PATCH 2/4] Add device tree ocontext nodes to Xen policy

On 12/03/15 17:32, Daniel De Graaf wrote: > On 03/12/2015 01:27 PM, Julien Grall wrote: >> Hi Daniel, >> >> On 12/03/15 17:12, Daniel De Graaf wrote: >>> ; >>> +dtree_context_def: DEVICETREECON path security_context_def >>> +{if (define_devicetree_context()) re

[Xen-devel] [PATCH V7 00/12] xen: Clean-up of mem_event subsystem

This patch series aims to clean up the mem_event subsystem within Xen. The original use-case for this system was to allow external helper applications running in privileged domains to control various memory operations performed by Xen. Amongs these were paging, sharing and access control. The subsy

[Xen-devel] [PATCH V7 10/12] xen/vm_event: Relocate memop checks

The memop handler function for paging/sharing responsible for calling XSM doesn't really have anything to do with vm_event, thus in this patch we relocate it into mem_paging_memop and mem_sharing_memop. This has already been the approach in mem_access_memop, so in this patch we just make it consist

[Xen-devel] [PATCH V7 03/12] xen/mem_paging: Convert mem_event_op to mem_paging_op and cleanup

The only use-case of the mem_event_op structure had been in mem_paging, thus renaming the structure mem_paging_op and relocating its associated functions clarifies its actual usage. As part of this fix-up we also convert the gfn's in the toolstack to be explicitely 64-bit wide and clean the code a

[Xen-devel] [PATCH V7 01/12] xen/mem_event: Cleanup of mem_event structures

The public mem_event structures used to communicate with helper applications via shared rings have been used in different settings. However, the variable names within this structure have not reflected this fact, resulting in the reuse of variables to mean different things under different scenarios.

[Xen-devel] [PATCH V7 06/12] x86/hvm: factor out and rename vm_event related functions

To avoid growing hvm.c these functions can be stored separately. Minor style changes are applied to the logic in the file. Signed-off-by: Tamas K Lengyel Acked-by: Kevin Tian Acked-by: Tim Deegan --- v6: Style fixes v5: Style fixes Fix hvm_event_msr input types to match the incoming variabl

[Xen-devel] [PATCH V7 09/12] xen/vm_event: Decouple vm_event and mem_access.

The vm_event subsystem has been artifically tied to the presence of mem_access. While mem_access does depend on vm_event, vm_event is an entirely independent subsystem that can be used for arbitrary function-offloading to helper apps in domains. This patch removes the dependency that mem_access nee

Re: [Xen-devel] Xen-unstable: "root=" no longer prepended on kernel cmdline since commit "tools: xl: handle unspecified extra= when dealing with root="

On Thu, 2015-03-12 at 18:48 +0100, Sander Eikelenboom wrote: > Hi Ian, > > My PV-guest configs were still using the old "root=" option, > but these guests don't boot anymore since: > commit 49ab17a3a615e1ab4ccc46d6942f925cf841df4b, > "tools: xl: handle unspecified extra= when dealing with root=" >

[Xen-devel] [PATCH V7 11/12] xen/xsm: Split vm_event_op into three separate labels

The XSM label vm_event_op has been used to control the three memops controlling mem_access, mem_paging and mem_sharing. While these systems rely on vm_event, these are not vm_event operations themselves. Thus, in this patch we introduce three separate labels for each of these memops. Signed-off-by

[Xen-devel] [PATCH V7 04/12] xen: Rename mem_event to vm_event

In this patch we mechanically rename mem_event to vm_event. This patch introduces no logic changes to the code. Using the name vm_event better describes the intended use of this subsystem, which is not limited to memory events. It can be used for off-loading the decision making logic into helper ap

[Xen-devel] [PATCH V7 12/12] xen/vm_event: Add RESUME option to vm_event_op domctl

Thus far mem_access and mem_sharing memops had been able to signal to Xen to start pulling responses off the corresponding rings. In this patch we retire these memops and add them to the option to the vm_event_op domctl. The vm_event_op domctl suboptions are the same for each ring thus we consolid

[Xen-devel] [PATCH V7 07/12] xen: Introduce monitor_op domctl

In preparation for allowing for introspecting ARM and PV domains the old control interface via the hvm_op hypercall is retired. A new control mechanism is introduced via the domctl hypercall: monitor_op. This patch aims to establish a base API on which future applications can build on. Suggested-

[Xen-devel] [PATCH V7 08/12] xen/vm_event: Deprecate VM_EVENT_FLAG_DUMMY flag

There are no use-cases for this flag. Signed-off-by: Tamas K Lengyel Acked-by: Tim Deegan --- xen/arch/x86/mm/mem_sharing.c | 3 --- xen/arch/x86/mm/p2m.c | 3 --- xen/common/mem_access.c | 3 --- xen/include/public/vm_event.h | 1 - 4 files changed, 10 deletions(-) diff --git a/

[Xen-devel] [PATCH V7 05/12] tools/tests: Clean-up tools/tests/xen-access

The spin-lock implementation in the xen-access test program is implemented in a fashion that is actually incomplete. The x86 assembly that guarantees that the lock is held by only one thread lacks the "lock;" instruction. However, the spin-lock is not actually necessary in xen-access as it is not

[Xen-devel] [PATCH V7 02/12] xen/mem_event: Cleanup mem_event names in rings, functions and domctls

The name of one of the mem_event rings still implies it is used only for memory accesses, which is no longer the case. It is also used to deliver various HVM events, thus the name "monitor" is more appropriate in this setting. Couple functions incorrectly labeled as part of mem_event is also renam

Re: [Xen-devel] [PATCH] xsm: add device tree labeling support

On 03/12/2015 01:13 PM, Daniel De Graaf wrote: This adds support in the hypervisor and policy build toolchain for Xen/Flask policy version 25, which adds the ability to label ARM device tree nodes and expands the IOMEM ocontext entries to 64 bits. Signed-off-by: Daniel De Graaf --- Note: Actua

Re: [Xen-devel] [PATCH 3/4] checkpolicy: add output for Xen policy version support

On 03/12/2015 01:12 PM, Daniel De Graaf wrote: > When invoked as "checkpolicy -t Xen -V", report the range of supported > versions for the Xen policy instead of the supported versions for the > SELinux policy. > > This also changes the default maximum policy version to depend on the > policy type,

[Xen-devel] Xen-unstable: "root=" no longer prepended on kernel cmdline since commit "tools: xl: handle unspecified extra= when dealing with root="

Hi Ian, My PV-guest configs were still using the old "root=" option, but these guests don't boot anymore since: commit 49ab17a3a615e1ab4ccc46d6942f925cf841df4b, "tools: xl: handle unspecified extra= when dealing with root=" These pv guests don't boot anymore since the "root=" part isn't prepended

Re: [Xen-devel] [PATCH 2/2] xen: arm: more flexible scheme for specifying early printk device

At 16:51 + on 12 Mar (1426175517), Ian Campbell wrote: > On Thu, 2015-03-12 at 12:03 +0100, Tim Deegan wrote: > > CONFIG_EARLY_PRINTK := $(or $(EARLY_PRINTK_$(CONFIG_EARLY_PRINTK)), > > $(CONFIG_EARLY_PRINTK) > > EARLY_PRINTK_CFG := $(subst $(COMMA), ,$(CONFIG_EARLY_PRINTK)) > > I didn't know

Re: [Xen-devel] [PATCH 1/4] Expand Xen IOMEMCON to 64 bits

Hi Daniel, On 12/03/15 17:12, Daniel De Graaf wrote: > diff --git a/libsepol/src/write.c b/libsepol/src/write.c > index d03dc20..d98a5eb 100644 > --- a/libsepol/src/write.c > +++ b/libsepol/src/write.c > @@ -1252,13 +1252,24 @@ static int ocontext_write_xen(struct > policydb_compat_info *info, po

Re: [Xen-devel] [PATCH 2/4] Add device tree ocontext nodes to Xen policy

On 03/12/2015 01:27 PM, Julien Grall wrote: Hi Daniel, On 12/03/15 17:12, Daniel De Graaf wrote: ; +dtree_context_def : DEVICETREECON path security_context_def + {if (define_devicetree_context()) return -1;} + ; The rege

Re: [Xen-devel] [PATCH 2/4] Add device tree ocontext nodes to Xen policy

Hi Daniel, On 12/03/15 17:12, Daniel De Graaf wrote: > ; > +dtree_context_def: DEVICETREECON path security_context_def > + {if (define_devicetree_context()) return -1;} > + ; The regex for matching the device tree path is different

[Xen-devel] [PATCH v2 3/3] xen: arm: handle PCI DT node ranges and interrupt-map properties

These properties are defined in ePAPR (2.3.8 and 2.4.3.1 respectively) and the OpenFirmware PCI Bus Binding Specification (IEEE Std 1275-1994). This replaces the xgene specific mapping. Tested on Mustang and on a model with a PCI virtio controller. TODO: Use a helper iterator (e.g. dt_for_each_ra

[Xen-devel] [PATCH v2 1/3] xen: dt: add dt_for_each_irq_map helper

This function iterates over a nodes interrupt-map property and calls a callback for each interrupt. For now it only supplies the raw IRQ since my use case has no need of e.g. child unit address. These can be added as needed by any future users. This follows much the same logic as dt_irq_map_raw wh

[Xen-devel] [PATCH v2 2/3] xen: arm: propagate gic's #interrupt-cells property to dom0.

This is similar to 816f5bb1f074 "xen: arm: propagate gic's should propagate (rather than invent our own value) since this value is used to size fields within other properties within the tree. I'm not sure why I didn't do this as part of 816f5bb1f074. I think probably just because #interrupt-cells

[Xen-devel] [PATCH v2 0/3] xen: arm: Parse PCI DT nodes' ranges and interrupt-map

This series adds parsing of the DT ranges and interrupt-map properties for PCI devices, these contain the MMIOs and IRQs used by children on the bus. This replaces the specific mapping stuff on xgene. This is pretty much a rewrite of v1, which was wrong in several aspects relating to its parsing o

[Xen-devel] [PATCH 4/4] checkpolicy: Expand allowed character set in paths

In order to support paths containing spaces or other characters, allow a quoted string with these characters to be parsed as a path in addition to the existing unquoted string. Signed-off-by: Daniel De Graaf --- checkpolicy/policy_parse.y | 3 +++ checkpolicy/policy_scan.l | 1 + 2 files change

[Xen-devel] [PATCH 0/4] Xen/FLASK policy updates for device contexts

In order to support assigning security lables to ARM device tree nodes in Xen's XSM policy, a new ocontext type is needed in the security policy. This addition requires a new policy version for Xen. In order to keep the build process for Xen policy sane, a method of determining the highest Xen po

[Xen-devel] [PATCH] xsm: add device tree labeling support

This adds support in the hypervisor and policy build toolchain for Xen/Flask policy version 25, which adds the ability to label ARM device tree nodes and expands the IOMEM ocontext entries to 64 bits. Signed-off-by: Daniel De Graaf --- Note: Actually using the features added in this patch requir

[Xen-devel] [PATCH 2/4] Add device tree ocontext nodes to Xen policy

In Xen on ARM, device tree nodes identified by a path (string) need to be labeled by the security policy. Signed-off-by: Daniel De Graaf --- checkpolicy/policy_define.c| 55 + checkpolicy/policy_define.h| 1 + checkpolicy/policy_parse.y

[Xen-devel] [PATCH 3/4] checkpolicy: add output for Xen policy version support

When invoked as "checkpolicy -t Xen -V", report the range of supported versions for the Xen policy instead of the supported versions for the SELinux policy. This also changes the default maximum policy version to depend on the policy type, so that running "checkpolicy -t Xen" without -c does not f

[Xen-devel] [PATCH 1/4] Expand Xen IOMEMCON to 64 bits

This change is required to support static I/O memory range labeling for systems with over 16TB of physical address space. Signed-off-by: Daniel De Graaf --- checkpolicy/policy_define.c| 6 +++--- checkpolicy/policy_define.h| 2 +- checkpolicy/policy_parse.y

Re: [Xen-devel] [PATCH V13 1/7] xen/arm: p2m changes for mem_access support

On Thu, 2015-03-12 at 16:56 +, Julien Grall wrote: > On 12/03/15 14:10, Andrew Cooper wrote: > > On 12/03/15 13:56, Ian Campbell wrote: > >> On Thu, 2015-03-12 at 12:57 +, Julien Grall wrote: > >>> Hi Tamas, > >>> > >>> On 06/03/15 21:24, Tamas K Lengyel wrote: > @@ -1090,6 +1098,8 @@

Re: [Xen-devel] [PATCH v1 2/3] sched_credit2.c : runqueue_per_core code

On Thu, 2015-03-12 at 16:21 +, Jan Beulich wrote: > >>> On 12.03.15 at 15:57, wrote: > > @@ -1940,10 +1946,14 @@ static void init_pcpu(const struct scheduler *ops, > > int cpu) > > > > /* Figure out which runqueue to put it in */ > > /* NB: cpu 0 doesn't get a STARTING callback,

Re: [Xen-devel] [PATCH V13 1/7] xen/arm: p2m changes for mem_access support

On 12/03/15 14:10, Andrew Cooper wrote: > On 12/03/15 13:56, Ian Campbell wrote: >> On Thu, 2015-03-12 at 12:57 +, Julien Grall wrote: >>> Hi Tamas, >>> >>> On 06/03/15 21:24, Tamas K Lengyel wrote: @@ -1090,6 +1098,8 @@ void p2m_teardown(struct domain *d) p2m_free_vmid(d)

Re: [Xen-devel] [PATCH] libxl: remove LIBXL_MAXMEM_CONSTANT

On Thu, 12 Mar 2015, Ian Campbell wrote: > On Thu, 2015-03-12 at 11:02 +, Stefano Stabellini wrote: > > On Thu, 26 Feb 2015, Ian Campbell wrote: > > > On Thu, 2015-02-26 at 12:19 +, Stefano Stabellini wrote: > > > > On Wed, 25 Feb 2015, Don Slutz wrote: > > > > > On 02/25/15 10:07, Stefano

Re: [Xen-devel] [PATCH V13 4/7] xen/arm: Data abort exception (R/W) mem_events.

On 12/03/15 15:46, Ian Campbell wrote: > On Thu, 2015-03-12 at 15:37 +, Julien Grall wrote: >> On 12/03/15 15:26, Tamas K Lengyel wrote: >>> >>> >>> On Thu, Mar 12, 2015 at 4:13 PM, Julien Grall >> > wrote: >>> >>> Hi Tamas, >>> >>> On 06/03/15 21:24, Tam

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, Mar 12, 2015 at 5:48 PM, Ian Campbell wrote: > On Thu, 2015-03-12 at 17:02 +0100, Tamas K Lengyel wrote: > > > > > > On Thu, Mar 12, 2015 at 4:56 PM, Ian Campbell > > wrote: > > On Thu, 2015-03-12 at 16:44 +0100, Tamas K Lengyel wrote: > > > > > > > > > On

Re: [Xen-devel] [PATCH 2/2] xen: arm: more flexible scheme for specifying early printk device

On Thu, 2015-03-12 at 12:03 +0100, Tim Deegan wrote: > At 14:11 + on 11 Mar (1426079515), Ian Campbell wrote: > > +EARLY_PRINTK_brcm := 8250,0xF040AB00,2 > > +EARLY_PRINTK_dra7 := 8250,0x4806A000,2 > > +EARLY_PRINTK_fastmodel := pl011,0x1c09,115200 > > +EARLY_PRINTK

Re: [Xen-devel] [PATCH v3 4/4] libxl: add support for vscsi

On Thu, 2015-03-12 at 17:07 +0100, Olaf Hering wrote: > On Wed, Mar 11, Ian Campbell wrote: > > > On Fri, 2015-03-06 at 10:45 +0100, Olaf Hering wrote: > > > +void libxl_device_vscsi_append_dev(libxl_ctx *ctx, libxl_device_vscsi > > > *hst, > > > + libxl_vscsi_de

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, 2015-03-12 at 17:02 +0100, Tamas K Lengyel wrote: > > > On Thu, Mar 12, 2015 at 4:56 PM, Ian Campbell > wrote: > On Thu, 2015-03-12 at 16:44 +0100, Tamas K Lengyel wrote: > > > > > > On Thu, Mar 12, 2015 at 4:40 PM, Julien Grall > > wrote: >

Re: [Xen-devel] [PATCH v2] x86/EFI: allow reboot= overrides when running under EFI

On 12/03/15 16:32, Jan Beulich wrote: > By default we will always use EFI reboot mechanism when > running under EFI platforms. However some EFI platforms > are buggy and need to use the ACPI mechanism to > reboot (such as Lenovo ThinkCentre M57). As such > respect the 'reboot=' override and DMI ove

Re: [Xen-devel] [PATCH v3 4/4] libxl: add support for vscsi

On Thu, 2015-03-12 at 17:20 +0100, Olaf Hering wrote: > On Wed, Mar 11, Ian Campbell wrote: > > > On Fri, 2015-03-06 at 10:45 +0100, Olaf Hering wrote: > > > +int libxl_device_vscsi_parse_pdev(libxl__gc *gc, char *pdev, unsigned > > > int *hst, > > > +unsigned int

Re: [Xen-devel] [PATCH v1 1/3] x86: identifying the boot cpu

On 03/12/2015 10:55 AM, Uma Sharma wrote: Provide helpers to access the socket and core IDs, resulting from identification phase. Initialize socket and core ID to -1 i.e invalid instead of 0. Signed-off-by: Uma Sharma --- xen/arch/x86/setup.c| 7 +-- xen/arch/x86/smpboot.c

[Xen-devel] [PATCH v2] x86/EFI: allow reboot= overrides when running under EFI

By default we will always use EFI reboot mechanism when running under EFI platforms. However some EFI platforms are buggy and need to use the ACPI mechanism to reboot (such as Lenovo ThinkCentre M57). As such respect the 'reboot=' override and DMI overrides for EFI platforms. Signed-off-by: Konrad

Re: [Xen-devel] [PATCH V13 4/7] xen/arm: Data abort exception (R/W) mem_events.

Hi Ian, On 12/03/15 15:35, Ian Campbell wrote: > On Thu, 2015-03-12 at 16:19 +0100, Tamas K Lengyel wrote: >> >>> out: >> > +if ( flush ) >> > +{ >> > +flush_tlb_domain(d); >> > +iommu_iotlb_flush(d, sgfn, egf

Re: [Xen-devel] [PATCH v1 2/3] sched_credit2.c : runqueue_per_core code

On Thu, 2015-03-12 at 16:21 +, Jan Beulich wrote: > >>> On 12.03.15 at 15:57, wrote: > > @@ -1940,10 +1946,14 @@ static void init_pcpu(const struct scheduler *ops, > > int cpu) > > > > /* Figure out which runqueue to put it in */ > > /* NB: cpu 0 doesn't get a STARTING callback,

Re: [Xen-devel] [PATCH] libxl: remove LIBXL_MAXMEM_CONSTANT

On Thu, 2015-03-12 at 11:02 +, Stefano Stabellini wrote: > On Thu, 26 Feb 2015, Ian Campbell wrote: > > On Thu, 2015-02-26 at 12:19 +, Stefano Stabellini wrote: > > > On Wed, 25 Feb 2015, Don Slutz wrote: > > > > On 02/25/15 10:07, Stefano Stabellini wrote: > > > > > LIBXL_MAXMEM_CONSTANT i

Re: [Xen-devel] Python Bindings Status

On Thu, 2015-03-12 at 11:02 +, James Dingwall wrote: > Hi, > > I am trying to use the libxl python bindings but having mixed levels of > success. I assume that the current > status of this is unsupported as the build of the xl.so is disabled by > default but perhaps completing the > missi

Re: [Xen-devel] Failed to launch xen on J6 evm

Hi Ian CONFIG_XEN iand CONFIG_HVC_XEN are enabled =y in .config other config settings seem to be in line. getty was not properly setup in my dom0 settings - thanks Regards Naveen Please note my new email address naveen.koru...@ext.us.panasonic.com. The old address will be available until Septem

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

All, I expect to have a patch out soon for the RTDS scheduler improvement. Regards, Dagaen Golomb On Thu, Mar 12, 2015 at 12:01 PM, Olaf Hering wrote: > On Thu, Mar 12, Ian Campbell wrote: > > > dist/install/var/xen/dump > > which all seems proper and correct to me. > > Except the last

Re: [Xen-devel] [PATCH v1 3/3] docs : documentation for the code

>>> On 12.03.15 at 15:59, wrote: > This patch inserts boot paramter documentation in xen-command-line.markdown. > > Signed-off-by: Uma Sharma > --- > docs/misc/xen-command-line.markdown | 7 +++ This should be merged into the patch introducing the option. Jan

Re: [Xen-devel] [PATCH v1 2/3] sched_credit2.c : runqueue_per_core code

>>> On 12.03.15 at 15:57, wrote: > @@ -161,10 +161,16 @@ > */ > #define __CSFLAG_runq_migrate_request 3 > #define CSFLAG_runq_migrate_request (1<<__CSFLAG_runq_migrate_request) > - > +/* CREDIT2_OPT_RUNQUEUE: Used to define the runqueue used > + */ > +#define CREDIT2_OPT_RUNQUEUE_CORE 1 > +#de

Re: [Xen-devel] [PATCH v3 4/4] libxl: add support for vscsi

On Wed, Mar 11, Ian Campbell wrote: > On Fri, 2015-03-06 at 10:45 +0100, Olaf Hering wrote: > > +int libxl_device_vscsi_parse_pdev(libxl__gc *gc, char *pdev, unsigned int > > *hst, > > +unsigned int *chn, unsigned int *tgt, > > +unsi

Re: [Xen-devel] [PATCH v1 3/3] docs : documentation for the code

On 12/03/15 14:59, Uma Sharma wrote: > This patch inserts boot paramter documentation in xen-command-line.markdown. > > Signed-off-by: Uma Sharma This change should be in the same patch which introduced the option. ~Andrew > --- > docs/misc/xen-command-line.markdown | 7 +++ > 1 file chang

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, Mar 12, 2015 at 4:55 PM, Ian Campbell wrote: > On Thu, 2015-03-12 at 16:41 +0100, Tamas K Lengyel wrote: > > > We could check stage-1 permissions by walking the guest page tables > > and looking at the pte permissions, however I'm not aware of having > > this function implemented within X

Re: [Xen-devel] [PATCH V6 11/13] xen/vm_event: Relocate memop checks

Hi, At 01:11 +0100 on 18 Feb (1424218301), Tamas K Lengyel wrote: > -int mem_paging_memop(struct domain *d, xen_mem_paging_op_t *mpo) > +int mem_paging_memop(XEN_GUEST_HANDLE_PARAM(xen_mem_paging_op_t) arg) > { > -int rc = -ENODEV; > -if ( unlikely(!d->vm_event->paging.ring_page) ) > +

Re: [Xen-devel] [PATCH v1 1/3] x86: identifying the boot cpu

>>> On 12.03.15 at 15:55, wrote: > Provide helpers to access the socket and core IDs, resulting from > identification phase. > Initialize socket and core ID to -1 i.e invalid instead of 0. You still don't say _why_ both of these are needed. > --- a/xen/arch/x86/smpboot.c > +++ b/xen/arch/x86/sm

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

On Thu, 2015-03-12 at 15:07 +, Ian Campbell wrote: > On Thu, 2015-03-12 at 10:21 +, wei.l...@citrix.com wrote: > > > * Repurpose SEDF Scheduler for Real-time (fair) > >RFC patch posted (v2) > > - Joshua Whitehead, Robert VanVossen > > This was superceded by the RTDS stuff, wasn't

Re: [Xen-devel] [PATCH V13 4/7] xen/arm: Data abort exception (R/W) mem_events.

On Thu, 2015-03-12 at 15:37 +, Julien Grall wrote: > On 12/03/15 15:26, Tamas K Lengyel wrote: > > > > > > On Thu, Mar 12, 2015 at 4:13 PM, Julien Grall > > wrote: > > > > Hi Tamas, > > > > On 06/03/15 21:24, Tamas K Lengyel wrote: > > > +

Re: [Xen-devel] [PATCH V13 4/7] xen/arm: Data abort exception (R/W) mem_events.

On Thu, 2015-03-12 at 16:19 +0100, Tamas K Lengyel wrote: > > > out: > > +if ( flush ) > > +{ > > +flush_tlb_domain(d); > > +iommu_iotlb_flush(d, sgfn, egfn - sgfn); > > +} >

Re: [Xen-devel] [PATCH V13 6/7] xen/arm: Enable mem_access on ARM

On Thu, Mar 12, 2015 at 4:19 PM, Julien Grall wrote: > Hi Tamas, > > On 06/03/15 21:24, Tamas K Lengyel wrote: > > Signed-off-by: Tamas K Lengyel > > It's strange to enable MEM_ACCESS before having the toolstack part > support memaccess (even though it's tiny). Made the series a bit more easie

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, Mar 12, 2015 at 4:40 PM, Julien Grall wrote: > Hi Ian, > > On 12/03/15 15:27, Ian Campbell wrote: > >> Currently, check_type_get_page emulate only the check for 2). So you may > >> end up to allow Xen writing in read-only mapping (from the Stage 1 POV). > >> This was XSA-98. > > > > XSA-9

Re: [Xen-devel] [PATCH v3 4/4] libxl: add support for vscsi

On Wed, Mar 11, Ian Campbell wrote: > On Fri, 2015-03-06 at 10:45 +0100, Olaf Hering wrote: > > +void libxl_device_vscsi_append_dev(libxl_ctx *ctx, libxl_device_vscsi *hst, > > + libxl_vscsi_dev *dev); > > +int libxl_device_vscsi_get_host(libxl_ctx *ctx, > > +

Re: [Xen-devel] [PATCH V13 4/7] xen/arm: Data abort exception (R/W) mem_events.

On 12/03/15 15:26, Tamas K Lengyel wrote: > > > On Thu, Mar 12, 2015 at 4:13 PM, Julien Grall > wrote: > > Hi Tamas, > > On 06/03/15 21:24, Tamas K Lengyel wrote: > > +/* > > + * Preempt setting mem_access permissions as required

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, Mar 12, 2015 at 4:56 PM, Ian Campbell wrote: > On Thu, 2015-03-12 at 16:44 +0100, Tamas K Lengyel wrote: > > > > > > On Thu, Mar 12, 2015 at 4:40 PM, Julien Grall > > wrote: > > Hi Ian, > > > > On 12/03/15 15:27, Ian Campbell wrote: > > >> Currently, check_type_ge

Re: [Xen-devel] [PATCH V6 13/13] xen/vm_event: Add RESUME option to vm_event_op domctl

On Thu, Mar 12, 2015 at 4:56 PM, Tim Deegan wrote: > At 01:11 +0100 on 18 Feb (1424218303), Tamas K Lengyel wrote: > > Thus far mem_access and mem_sharing memops had been able to signal > > to Xen to start pulling responses off the corresponding rings. In this > patch > > we retire these memops a

Re: [Xen-devel] Xen 4.6 Development Update (two months reminder)

On Thu, Mar 12, Ian Campbell wrote: > dist/install/var/xen/dump > which all seems proper and correct to me. Except the last one, which should be /var/lib/xen/dump or whatever dumpdir the OS/FHS provides. Olaf ___ Xen-devel mailing list Xen-dev

Re: [Xen-devel] [PATCH V6 00/13] xen: Clean-up of mem_event subsystem

Hi, At 01:11 +0100 on 18 Feb (1424218290), Tamas K Lengyel wrote: > This patch series aims to clean up the mem_event subsystem within Xen. The > original use-case for this system was to allow external helper applications > running in privileged domains to control various memory operations performe

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, 2015-03-12 at 15:40 +, Julien Grall wrote: > Hi Ian, > > On 12/03/15 15:27, Ian Campbell wrote: > >> Currently, check_type_get_page emulate only the check for 2). So you may > >> end up to allow Xen writing in read-only mapping (from the Stage 1 POV). > >> This was XSA-98. > > > > XSA

Re: [Xen-devel] [PATCH V13 3/7] xen/arm: Allow hypervisor access to mem_access protected pages

On Thu, 2015-03-12 at 16:41 +0100, Tamas K Lengyel wrote: > We could check stage-1 permissions by walking the guest page tables > and looking at the pte permissions, however I'm not aware of having > this function implemented within Xen. The h/w can do this for you, you just need to arrange for g

Re: [Xen-devel] [PATCH] xen: avoid updating node affinity twice when removing a CPU from a cpupool

On Thu, 2015-03-12 at 14:52 +, George Dunlap wrote: > On 03/12/2015 01:45 PM, Dario Faggioli wrote: > > Patch below, and attached. However, I think the correct thing to do > > would be to just revert 93be8285 "update domU's node-affinity on the > > cpupool_unassign_cpu() path", wouldn't it? >

  1   2   3   >