From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Dave Hansen <dave.hansen@intel.com>,
Ulrich Weigand <uweigand@de.ibm.com>
Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>,
viro@zeniv.linux.org.uk, david@redhat.com,
akpm@linux-foundation.org, aarcange@redhat.com,
linux-mm@kvack.org, frankja@linux.ibm.com, sfr@canb.auug.org.au,
jhubbard@nvidia.com, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org, jack@suse.cz, kirill@shutemov.name,
peterz@infradead.org, sean.j.christopherson@intel.com,
Ulrich.Weigand@de.ibm.com
Subject: Re: [PATCH v2 1/1] fs/splice: add missing callback for inaccessible pages
Date: Tue, 5 May 2020 16:00:10 +0200 [thread overview]
Message-ID: <45bc81bb-8765-ffff-6e47-8ee9702c8bcd@de.ibm.com> (raw)
In-Reply-To: <231da2f1-a6ef-0cf9-7f57-95e8b925997b@intel.com>
On 05.05.20 14:34, Dave Hansen wrote:[...]
>> I'm not sure what exactly the requirements for your use case are; if those
>> are significantly differently, maybe we can work together to find an
>> approach that works for both?
>
> I'm actually trying to figure out what to do with AMD's SEV. The
> current state isn't great and, for instance, allows userspace to read
> guest ciphertext. But, the pages come and go out of the encrypted state
> at the behest of the guest, and the kernel needs *some* mapping for the
> pages to do things like instruction emulation.
>
> I started looking at s390 because someone said there was a similar
> problem there and suggested the hooks might work. I couldn't figure out
> how they worked comprehensively on s390, and that's how we got here.
We are certainly not married to our approach. I would happily extend/change
this to anything that works for your case and the s390 case. So can you outline
your requirements a bit more?
next prev parent reply other threads:[~2020-05-05 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 14:38 Claudio Imbrenda
2020-04-30 20:04 ` Christian Borntraeger
2020-04-30 22:06 ` Dave Hansen
2020-04-30 22:20 ` Dave Hansen
2020-05-01 7:18 ` Christian Borntraeger
2020-05-01 16:32 ` Dave Hansen
2020-05-04 13:41 ` Ulrich Weigand
2020-05-05 12:34 ` Dave Hansen
2020-05-05 13:55 ` Ulrich Weigand
2020-05-05 14:01 ` Christian Borntraeger
2020-05-05 14:03 ` Christian Borntraeger
2020-05-05 14:33 ` Ulrich Weigand
2020-05-05 14:49 ` Christian Borntraeger
2020-05-05 14:57 ` Dave Hansen
2020-05-05 14:00 ` Christian Borntraeger [this message]
2020-05-05 14:24 ` Dave Hansen
2020-05-05 14:31 ` Christian Borntraeger
2020-05-05 14:34 ` Dave Hansen
2020-05-05 14:39 ` Christian Borntraeger
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=45bc81bb-8765-ffff-6e47-8ee9702c8bcd@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=uweigand@de.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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