All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "Mantas Mikulėnas" <grawity@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
	Matt Fleming <matt.fleming@intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Anders Darander <anders@chargestorm.se>,
	linux-efi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v4] x86: only load initrd above 4g on second try
Date: Mon, 8 Sep 2014 16:58:55 +0100	[thread overview]
Message-ID: <20140908155855.GS3001@console-pimps.org> (raw)
In-Reply-To: <CAPWNY8V6Vw0JBZ=VE_ZLZ1hiKVhrDbYyWfkLXMQtKYHZjmewRA@mail.gmail.com>

On Sat, 06 Sep, at 11:09:04PM, Mantas Mikulėnas wrote:
> 
> Finally got around to testing the patches here. Sorry for no replies earlier.
> 
> This seemed like it would work, but... it hangs at the memcpy?...
> 
> (If I add a printk before memcpy and a printk after memcpy, I never
> see the second one. I guess that memory location is just cursed, or
> something.)
 
Thanks for testing. Let's go ahead with Yinghai's patch ("x86/efi: Only
load initrd above 4g on second try").

-- 
Matt Fleming, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "Mantas Mikulėnas" <grawity-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	Yinghai Lu <yinghai-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Matt Fleming
	<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Anders Darander <anders-7UjN0b3lYz2SbKU13Z4Etw@public.gmane.org>,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH -v4] x86: only load initrd above 4g on second try
Date: Mon, 8 Sep 2014 16:58:55 +0100	[thread overview]
Message-ID: <20140908155855.GS3001@console-pimps.org> (raw)
In-Reply-To: <CAPWNY8V6Vw0JBZ=VE_ZLZ1hiKVhrDbYyWfkLXMQtKYHZjmewRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Sat, 06 Sep, at 11:09:04PM, Mantas Mikulėnas wrote:
> 
> Finally got around to testing the patches here. Sorry for no replies earlier.
> 
> This seemed like it would work, but... it hangs at the memcpy?...
> 
> (If I add a printk before memcpy and a printk after memcpy, I never
> see the second one. I guess that memory location is just cursed, or
> something.)
 
Thanks for testing. Let's go ahead with Yinghai's patch ("x86/efi: Only
load initrd above 4g on second try").

-- 
Matt Fleming, Intel Open Source Technology Center

  parent reply	other threads:[~2014-09-08 15:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  4:50 [PATCH -v4] x86: only load initrd above 4g on second try Yinghai Lu
2014-09-04  4:50 ` Yinghai Lu
2014-09-04 10:01 ` Matt Fleming
2014-09-04 20:59   ` H. Peter Anvin
2014-09-04 21:29     ` Matt Fleming
2014-09-05  1:19       ` Yinghai Lu
2014-09-05  1:19         ` Yinghai Lu
2014-09-05  5:47         ` Anders Darander
2014-09-05  5:47           ` Anders Darander
2014-09-05  6:38           ` Laszlo Ersek
2014-09-05 17:03             ` Yinghai Lu
2014-09-05 17:03               ` Yinghai Lu
2014-09-05 19:20               ` Laszlo Ersek
2014-09-05 19:20                 ` Laszlo Ersek
2014-09-05 22:16     ` Matt Fleming
2014-09-05 22:16       ` Matt Fleming
2014-09-06 19:05       ` Anders Darander
2014-09-06 19:05         ` Anders Darander
2014-09-06 20:09       ` Mantas Mikulėnas
2014-09-06 20:10         ` Mantas Mikulėnas
2014-09-08 15:58         ` Matt Fleming [this message]
2014-09-08 15:58           ` Matt Fleming

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=20140908155855.GS3001@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=anders@chargestorm.se \
    --cc=grawity@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.