[Top] [All Lists]

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

[Xen-devel] [PATCH v2 0/2] x86: XSA-246 / -247 follow-up

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Wed, 20 Dec 2017 02:25:00 -0700
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Delivery-date: Wed, 20 Dec 2017 09:25:03 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

1: PoD: correctly handle non-order-0 decrease-reservation requests
2: p2m: force return value checking of p2m_set_entry()

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>


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

Follow-Ups:
- [Xen-devel] [PATCH v2 2/2] x86/p2m: force return value checking of p2m_set_entry()
  - From: Jan Beulich
- [Xen-devel] [PATCH v2 1/2] x86/PoD: correctly handle non-order-0 decrease-reservation requests
  - From: Jan Beulich

References:
- [Xen-devel] [PATCH 0/3] x86: XSA-246 / -247 follow-up
  - From: Jan Beulich

Prev by Date: [Xen-devel] [PATCH v2] simplify xenmem_add_to_physmap_batch()
Next by Date: [Xen-devel] [PATCH v2 1/2] x86/PoD: correctly handle non-order-0 decrease-reservation requests
Previous by thread: Re: [Xen-devel] [PATCH 3/3] x86/p2m: force return value checking of p2m_set_entry()
Next by thread: [Xen-devel] [PATCH v2 1/2] x86/PoD: correctly handle non-order-0 decrease-reservation requests
Index(es):
- Date
- Thread

Rackspace

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