Re: [Xen-devel] [RFC 3/6] Introduce _xrealloc

On Thu, 8 Jun 2017, Sameer Goel wrote: > Introduce a memory realloc function. > > Signed-off-by: Sameer Goel > --- > xen/common/xmalloc_tlsf.c | 13 + > xen/include/xen/xmalloc.h | 1 + > 2 files changed, 14 insertions(+) > > diff --git

Re: [Xen-devel] [RFC 2/6] arm64: Add definitions for fwnode_handle

On Thu, 8 Jun 2017, Goel, Sameer wrote: > >> diff --git a/xen/include/xen/fwnode.h b/xen/include/xen/fwnode.h > >> new file mode 100644 > >> index 000..db65b15 > >> --- /dev/null > >> +++ b/xen/include/xen/fwnode.h > >> @@ -0,0 +1,35 @@ > >> +/* > >> + * fwnode.h - Firmware device node object

[Xen-devel] linux-next: bad commit in the xen-tip tree

Hi all, The current top commit of the xen-tip tree 9e925824eccd ("xen: avoid type warning in xchg_xen_ulong") has no Signed-off-by for its committer. -- Cheers, Stephen Rothwell ___ Xen-devel mailing list Xen-devel@lists.xen.org

Re: [Xen-devel] [PATCH v6 10/34] x86, x86/mm, x86/xen, olpc: Use __va() against just the physical address in cr3

On 08/06/2017 22:17, Boris Ostrovsky wrote: > On 06/08/2017 05:02 PM, Tom Lendacky wrote: >> On 6/8/2017 3:51 PM, Boris Ostrovsky wrote: > What may be needed is making sure X86_FEATURE_SME is not set for PV > guests. And that may be something that Xen will need to control through

Re: [Xen-devel] linux-next: bad commit in the xen-tip tree

On Fri, 9 Jun 2017, Stephen Rothwell wrote: > Hi all, > > The current top commit of the xen-tip tree > > 9e925824eccd ("xen: avoid type warning in xchg_xen_ulong") > > has no Signed-off-by for its committer. Fixed, thanks for pointing it out. ___

Re: [Xen-devel] [RFC 6/6] acpi:arm64: Add support for parsing IORT table

CCing Jan On Thu, 8 Jun 2017, Sameer Goel wrote: > Add limited support for parsing IORT table to initialize SMMU devices. > > Signed-off-by: Sameer Goel > --- > xen/arch/arm/setup.c| 3 + > xen/drivers/acpi/Makefile | 1 + >

Re: [Xen-devel] [PATCH 0/4] xenfb: Add vkbd-only option

On Thu, 8 Jun 2017, Owen Smith wrote: > Adds the ability for a vkbd device to connect without the > QemuConsole, in order to support a standalone PV mouse and > keyboard frontend. > This series adds a new feature flag, which will need adding > to the xen's include/public/io/kbdif.h Please do so,

Re: [Xen-devel] [PATCH 1/4] xenfb: Add feature-vkbd-standalone

On Thu, 8 Jun 2017, Owen Smith wrote: > Advertise "feature-vkbd-standalone" to indicate the backend > can connect without a vfb device connection. > When "request-vkbd-standalone" is set to 1, the backend does > not wait for a QemuConsole to be setup before connecting the > vkbd device. This also

Re: [Xen-devel] [PATCH 2/4] xenfb: Activate mouse handler

On Thu, 8 Jun 2017, Owen Smith wrote: > Mouse events are only delivered to the first handler in the chain. > Activating the xenfb mouse event handler so that mouse events can > be passed over the shared ring protocol. > Note: The keyboard handler is activated internally by the add > call. I am

Re: [Xen-devel] [for-4.9] Re: HVM guest performance regression

Bringing in Konrad because... On Thu, 2017-06-08 at 11:37 +0200, Juergen Gross wrote: > On 07/06/17 20:19, Stefano Stabellini wrote: > > On Wed, 7 Jun 2017, Juergen Gross wrote: > > > On 06/06/17 21:08, Stefano Stabellini wrote: > > > > > > > > 2) PV suspend/resume > > > > 3) vector callback > >

Re: [Xen-devel] [PATCH v6 10/34] x86, x86/mm, x86/xen, olpc: Use __va() against just the physical address in cr3

On 6/8/2017 3:51 PM, Boris Ostrovsky wrote: What may be needed is making sure X86_FEATURE_SME is not set for PV guests. And that may be something that Xen will need to control through either CPUID or MSR support for the PV guests. Only on newer versions of Xen. On earlier versions (2-3

Re: [Xen-devel] [RFC 2/6] arm64: Add definitions for fwnode_handle

On 6/8/2017 1:59 PM, Julien Grall wrote: > > > On 08/06/2017 20:30, Sameer Goel wrote: >> This will be used as a device property to match the DMA capable devices >> with the associated SMMU. The header file is a port from linux. >> >> Linux ChangeId:ce793486e23e: driver core / ACPI: Represent

Re: [Xen-devel] [PATCH v6 10/34] x86, x86/mm, x86/xen, olpc: Use __va() against just the physical address in cr3

> >> What may be needed is making sure X86_FEATURE_SME is not set for PV >> guests. > > And that may be something that Xen will need to control through either > CPUID or MSR support for the PV guests. Only on newer versions of Xen. On earlier versions (2-3 years old) leaf 0x8007 is passed

Re: [Xen-devel] [PATCH v6 10/34] x86, x86/mm, x86/xen, olpc: Use __va() against just the physical address in cr3

On 06/08/2017 05:02 PM, Tom Lendacky wrote: > On 6/8/2017 3:51 PM, Boris Ostrovsky wrote: >> >>> What may be needed is making sure X86_FEATURE_SME is not set for PV guests. >>> >>> And that may be something that Xen will need to control through either >>> CPUID or MSR support for the PV

Re: [Xen-devel] [PATCH 0/5] xen/pvh*: Support > 32 VCPUs at restore

On Thu, Jun 08, 2017 at 10:28:15AM +0200, Juergen Gross wrote: > On 03/06/17 02:05, Ankur Arora wrote: > > This patch series fixes a bunch of issues in the xen_vcpu setup > > logic. > > > > Simplify xen_vcpu related code: code refactoring in advance of the > > rest of the patch series. > > > >

[Xen-devel] Delivery Status Notification (Delay)

** Delivery incomplete ** There was a temporary problem delivering your message to curtiskwo...@gmail.com. Gmail will retry for 47 more hours. You'll be notified if the delivery fails permanently. Reporting-MTA: dns; googlemail.com Received-From-MTA: dns;

<    1   2   3