[RFC v1 0/2] Plumbing to support multiple secure memory backends. · Ram Pai <hidden> · 2020-10-12
[RFC v1 1/2] KVM: PPC: Book3S HV: rename all variables in book3s_hv_uvmem.c · Ram Pai <hidden> · 2020-10-12
[RFC v1 2/2] KVM: PPC: Book3S HV: abstract secure VM related calls. · Ram Pai <hidden> · 2020-10-12
Re: [RFC v1 2/2] KVM: PPC: Book3S HV: abstract secure VM related calls. · Bharata B Rao <hidden> · 2020-10-12
Re: [RFC v1 2/2] KVM: PPC: Book3S HV: abstract secure VM related calls. · Ram Pai <hidden> · 2020-10-12
Re: [RFC v1 0/2] Plumbing to support multiple secure memory backends. · Christoph Hellwig <hch@infradead.org> · 2020-10-14
RE: [RFC v1 0/2] Plumbing to support multiple secure memory backends. · Ram Pai <hidden> · 2020-10-14

Re: [RFC v1 0/2] Plumbing to support multiple secure memory backends.

From: Christoph Hellwig <hch@infradead.org>
Date: 2020-10-14 06:32:43

Please don't add an abstraction without a second implementation.
Once we have the implementation we can consider the tradeoffs.  E.g.
if expensive indirect function calls are really needed vs simple
branches.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help