From: Christoph Hellwig <hch@infradead.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: bharata@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
kvm-ppc@vger.kernel.org, farosas@linux.ibm.com
Subject: Re: [RFC v1 0/2] Plumbing to support multiple secure memory backends.
Date: Wed, 14 Oct 2020 07:31:17 +0100 [thread overview]
Message-ID: <20201014063117.GA26161@infradead.org> (raw)
In-Reply-To: <1602487663-7321-1-git-send-email-linuxram@us.ibm.com>
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.
next prev parent reply other threads:[~2020-10-14 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 7:27 [RFC v1 0/2] Plumbing to support multiple secure memory backends Ram Pai
2020-10-12 7:27 ` [RFC v1 1/2] KVM: PPC: Book3S HV: rename all variables in book3s_hv_uvmem.c Ram Pai
2020-10-12 7:27 ` [RFC v1 2/2] KVM: PPC: Book3S HV: abstract secure VM related calls Ram Pai
2020-10-12 15:28 ` Bharata B Rao
2020-10-12 16:13 ` Ram Pai
2020-10-14 6:31 ` Christoph Hellwig [this message]
2020-10-14 19:30 ` [RFC v1 0/2] Plumbing to support multiple secure memory backends Ram Pai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201014063117.GA26161@infradead.org \
--to=hch@infradead.org \
--cc=bharata@linux.ibm.com \
--cc=farosas@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).