From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
jgross@suse.com, dunlapg@umich.edu,
"Dr. Greg Wettstein" <greg@wind.enjellic.com>,
"Dr . Greg Wettstein" <greg@enjellic.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] tpm: Restore functionality to xen vtpm driver.
Date: Sun, 16 Sep 2018 22:25:10 +0300 [thread overview]
Message-ID: <20180916192510.GF7473@linux.intel.com> (raw)
In-Reply-To: <20180913212551.2435-1-boris.ostrovsky@oracle.com>
On Thu, Sep 13, 2018 at 05:25:51PM -0400, Boris Ostrovsky wrote:
> From: "Dr. Greg Wettstein" <greg@wind.enjellic.com>
>
> Functionality of the xen-tpmfront driver was lost secondary to
> the introduction of xenbus multi-page support in commit ccc9d90a9a8b
> ("xenbus_client: Extend interface to support multi-page ring").
>
> In this commit a pointer to the shared page address was being
> passed to the xenbus_grant_ring() function rather then the
> address of the shared page itself. This resulted in a situation
I'm sorry but I'm far from being expert with Xen and this sentence
confuses me so maybe could open it up a bit.
For me "shared page address" and "address of the shared page" are
the same thing. What am I missing? I mean just different forms in
english to describe the exact same thing...
/Jarkko
next prev parent reply other threads:[~2018-09-17 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 21:25 [PATCH v2] tpm: Restore functionality to xen vtpm driver Boris Ostrovsky
2018-09-16 19:25 ` Jarkko Sakkinen [this message]
2018-09-17 13:54 ` Boris Ostrovsky
2018-09-17 21:19 ` Jarkko Sakkinen
2018-09-17 22:25 ` Boris Ostrovsky
2018-09-18 6:54 ` [Xen-devel] " Dag Nygren
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=20180916192510.GF7473@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dunlapg@umich.edu \
--cc=greg@enjellic.com \
--cc=greg@wind.enjellic.com \
--cc=jgg@ziepe.ca \
--cc=jgross@suse.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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).