[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xen/mem-reservation API and out-of-tree kernel modules

To: Stefano Stabellini <sstabellini@xxxxxxxxxx>
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 1 Feb 2019 00:27:10 -0800
Cc: Juergen Gross <jgross@xxxxxxxx>, Oleksandr Andrushchenko <Oleksandr_Andrushchenko@xxxxxxxx>, "marmarek@xxxxxxxxxxxxxxxxxxxxxx" <marmarek@xxxxxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
Delivery-date: Fri, 01 Feb 2019 08:27:26 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Thu, Jan 31, 2019 at 01:44:15PM -0800, Stefano Stabellini wrote:
> The alternative would be to turn xenmem_reservation_scrub_page into a
> regular function (not a static inline)?

All that is a moot point until said currently out of tree module gets
submitted for inclusion anyway.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

Follow-Ups:
- Re: [Xen-devel] xen/mem-reservation API and out-of-tree kernel modules
  - From: Oleksandr Andrushchenko

Prev by Date: Re: [Xen-devel] [PATCH SpectreV1+L1TF v5 3/9] x86/hvm: block speculative out-of-bound accesses
Next by Date: Re: [Xen-devel] xen/mem-reservation API and out-of-tree kernel modules
Previous by thread: Re: [Xen-devel] [PATCH SpectreV1+L1TF v5 3/9] x86/hvm: block speculative out-of-bound accesses
Next by thread: Re: [Xen-devel] xen/mem-reservation API and out-of-tree kernel modules
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.