public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jordan Justen <jordan.l.justen@intel.com>
To: "Duran, Leo" <leo.duran@amd.com>,
	"'Laszlo Ersek'" <lersek@redhat.com>,
	"'Gao, Liming'" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"Singh, Brijesh" <brijesh.singh@amd.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Fan, Jeff" <jeff.fan@intel.com>,
	"Agyeman, Prince" <prince.agyeman@intel.com>,
	"Wei, David" <david.wei@intel.com>
Subject: Re: [PATCH v3 0/4] BaseIoFifoLib
Date: Mon, 09 Jan 2017 14:41:28 -0800	[thread overview]
Message-ID: <148400168843.2527.7563495097385526507@jljusten-ivb> (raw)
In-Reply-To: <DM5PR12MB1243481A0A10158933A50CCEF9640@DM5PR12MB1243.namprd12.prod.outlook.com>

On 2017-01-09 08:37:38, Duran, Leo wrote:
> > -----Original Message-----
> > From: Laszlo Ersek [mailto:lersek@redhat.com]
> > Sent: Monday, January 09, 2017 9:14 AM
> > 
> > On 01/09/17 15:22, Duran, Leo wrote:
> > >
> > >> -----Original Message-----
> > >> From: Gao, Liming [mailto:liming.gao@intel.com]
> > >> Sent: Sunday, January 08, 2017 9:11 PM
> > >>
> > >> Leo:
> > >>   IoLib Library class is designed from the functionality, not code
> > >> implementation. So, many IO operations are included in this library
> > >> class. If developers want to use IO API, they only need to check IoLib
> > library class.
> > >> After add new APIs, we need to update all IoLib library instances to
> > >> implement them. And, if any library API implementation has the
> > >> different version, the full library instance will have to be copied
> > >> to another instance. I know your concern is to duplicate the library
> > >> implementation. But, I think this is the separate topic to optimize
> > >> the library implementation and reuse the same source file. Other
> > >> library instances may have the same issue. So, I suggest you submit
> > >> bugzilla for this optimization request. We will figure out the solution and
> > review it in this mail list.
> > >>
> > >
> > > I'm not sure I follow what you mean by an 'optimization request'.
> > 
> > I think under "optimization", Liming means eliminating code duplication
> > between IoLib library instances. That is, if I understand correctly, Liming and
> > Jordan suggest that you first add the new interfaces to the IoLib class header,
> > add (--> duplicate) the implementation to all library instances, then file a BZ
> > about eliminating code duplication between the library instances.
> > 
> > This is my understanding anyway.
> > 
> [Duran, Leo]  Thanks Lazlo... Unfortunately the 'ask' is still not clear to me.
> Liming,  I would appreciate some clarification.

Can you simplify the request down to what is needed, and not worry
about the 'IoFifoLib' implementation idea? Then put that into a
bugzilla feature request? I think that was Liming's request.

Would a reasonable example feature request be: "OVMF should detect
Secure Encrypted Virtualization mode, and if detected, it should not
use rep i/o instructions"

I think you should also try to provide details for how to detect SEV
mode in the feature request.

One situation that sounds familiar to me is
881813d7a93d9009c873515b043c41c4554779e4.

By the way, is this true? You simply cannot use those instructions?
It's not a matter of them being really slow, but they just don't work
at all?

-Jordan


  reply	other threads:[~2017-01-09 22:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 21:49 [PATCH v3 0/4] BaseIoFifoLib Leo Duran
2017-01-05 21:49 ` [PATCH v3 1/4] MdePkg: Add BaseIoFifoLib library Leo Duran
2017-01-05 21:49 ` [PATCH v3 2/4] Modify .DSC files that include UefiCpuPkg/CpuIo2Dxe/CpuIo2Dxe.inf Leo Duran
2017-01-06 11:23   ` Laszlo Ersek
2017-01-06 15:28     ` Duran, Leo
2017-01-05 21:49 ` [PATCH v3 3/4] Modify UefiCpuPkg/CpuIo2Dxe to use new BaseIoFifoLib library Leo Duran
2017-01-05 21:49 ` [PATCH v3 4/4] Modify QemuFwCfgLib " Leo Duran
2017-01-06 11:36   ` Laszlo Ersek
2017-01-06 15:31     ` Duran, Leo
2017-01-06  6:02 ` [PATCH v3 0/4] BaseIoFifoLib Gao, Liming
2017-01-06 11:12   ` Laszlo Ersek
2017-01-06 15:23     ` Duran, Leo
2017-01-07  0:49       ` Jordan Justen
2017-01-07 17:16         ` Duran, Leo
2017-01-09  3:10           ` Gao, Liming
2017-01-09 14:22             ` Duran, Leo
2017-01-09 14:30               ` Duran, Leo
2017-01-09 14:36                 ` Duran, Leo
2017-01-09 15:13               ` Laszlo Ersek
2017-01-09 16:37                 ` Duran, Leo
2017-01-09 22:41                   ` Jordan Justen [this message]
2017-01-10  5:33               ` Gao, Liming
2017-01-10  5:48                 ` Duran, Leo

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-list 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=148400168843.2527.7563495097385526507@jljusten-ivb \
    --to=devel@edk2.groups.io \
    /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