[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130923070841.GE7007@dhcp-16-126.nay.redhat.com>
Date: Mon, 23 Sep 2013 15:08:41 +0800
From: Dave Young <dyoung@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...e.de>,
Matt Fleming <matt@...sole-pimps.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
"H. Peter Anvin" <hpa@...or.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Vivek Goyal <vgoyal@...hat.com>, linux-efi@...r.kernel.org
Subject: Re: [PATCH -v2] EFI: Runtime services virtual mapping
On 09/23/13 at 08:29am, Borislav Petkov wrote:
> On Mon, Sep 23, 2013 at 01:47:41PM +0800, Dave Young wrote:
> > > + unsigned long size = md->num_pages << PAGE_SHIFT;
> > > +
> > > + efi_va -= size;
> > > + if (efi_va < EFI_VA_END) {
> > > + pr_warning(FW_WARN "VA address range overflow!\n");
> > > + return;
> > > + }
> > > +
> > > + /* Do the 1:1 map */
> > > + __map_region(md, md->phys_addr);
> > > +
> > > + /* Do the VA map */
> > > + __map_region(md, efi_va);
> >
> >
> > Could you add comment for above code? It's hard to understand the
> > twice mapping if one did not follow the old thread.
>
> Does that suffice:
>
> /*
> * Make sure the 1:1 mappings are present as a catch-all for b0rked firmware
> * which doesn't update all internal pointers after switching to virtual mode
> * and would otherwise crap on us.
> */
>
> ?
Yes, looks good. Thanks
>
> Btw, when you reply to a mail, please remove that quoted portion of it
> which you're not replying to - I had to scroll a bunch of screens down
> and I almost missed your reply. :)
Will do. I did notice the problem after I enter 'y' in mutt, sorry about it.
>
> Thanks.
>
> --
> Regards/Gruss,
> Boris.
>
> Sent from a fat crate under my desk. Formatting is fine.
> --
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists