All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Kiper <dkiper@net-space.pl>
To: Michael Chang <MChang@suse.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>,
	Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>,
	"dave@jikos.cz" <dave@jikos.cz>,
	"pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>,
	"terrelln@fb.com" <terrelln@fb.com>
Subject: Re: [PATCH] btrfs: disable zstd support for i386-pc
Date: Tue, 3 Mar 2020 17:59:12 +0100	[thread overview]
Message-ID: <20200303165912.oqj6ac662sbl4y2q@tomti.i.net-space.pl> (raw)
In-Reply-To: <20191119083404.GA7871@mazu>

On Tue, Nov 19, 2019 at 08:34:12AM +0000, Michael Chang wrote:
> On Fri, Nov 15, 2019 at 12:42:52PM +0100, Daniel Kiper wrote:
> > On Thu, Nov 14, 2019 at 09:53:54AM +0000, Michael Chang wrote:
> > > On Wed, Nov 13, 2019 at 12:00:50PM +0100, Daniel Kiper wrote:
> > > > On Thu, Nov 07, 2019 at 12:52:35PM +0100, Daniel Kiper wrote:
> > > > > On Wed, Nov 06, 2019 at 11:15:04AM -0800, Vladimir 'phcoder' Serbinenko wrote:
> > > > > > Please don't do it this way. The right solution is to move it to separate
> > > > > > module and include zstd module when needed. Not everybody uses btrfs
> > > > > > embedded area. I recommend not to use it. Using mbr gap or BBP is the
> > > > > > recommended way.
> > > > >
> > > > > I will put the cat among the pigeons. Maybe we should finally stop
> > > > > pretending that the GRUB supports small MBR gaps. Otherwise we will
> > > > > be fighting with such issues endlessly.
> > > >
> > > > Bumping the thread... Nobody objects? Hmmm...
> > >
> > > I don't think we are able to give up MBR gap support, simply because no
> > > other way out in creating the area for bootloader embedding. However we
> >
> > Nope, I do not propose that...
> >
> > > should consider to correct this claim in manual.
> > >
> > >  "You must ensure that the first partition starts at least 31 KiB (63
> > >  sectors) from the start of the disk"
> > >
> > > to reflect the fact that 31 KiB is no longer applicable and the ideal
> > > size should be above 1MB (or such). You should go check with your disk
> > > tools to find the suitable parameter to fulfill the requirement, for eg,
> > > the partition alignment would mostly affect this.
> >
> > Exactly! However, there are some legacy systems which do not boot if MBR
> > gap does not end at 63 sectors boundary. Hence, maybe we should suggest
> > chainloading, using e.g. SYSLINUX, in a such cases. Anyway, may I ask
> > you to prepare a patch for GRUB manual which describes the problem?
>
> Alright, sounds good to me. :)

Michael, ping? I would like to see this limitation documented in 2.06.
Could you do that?

Daniel


  reply	other threads:[~2020-03-03 16:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  9:19 [PATCH] btrfs: disable zstd support for i386-pc Michael Chang
2019-11-05 10:52 ` Paul Menzel
2019-11-07  4:22   ` Michael Chang
2019-11-06 12:40 ` David Sterba
2019-11-06 18:53   ` Nick Terrell
2019-11-07  6:34   ` Michael Chang
2019-11-06 19:15 ` Vladimir 'phcoder' Serbinenko
2019-11-07  4:55   ` Michael Chang
2019-11-07  5:08     ` Vladimir 'phcoder' Serbinenko
2019-11-07  6:59       ` Michael Chang
2020-06-11 22:58       ` Eli Schwartz
2020-06-21 18:26         ` Mike Gilbert
2020-06-21 18:56           ` Eli Schwartz
2020-06-23  1:59             ` Mike Gilbert
2020-06-23  2:16             ` Mike Gilbert
2020-06-23  6:32               ` Michael Chang
2020-06-23 17:50                 ` Mike Gilbert
2019-11-07 11:52   ` Daniel Kiper
2019-11-13 11:00     ` Daniel Kiper
2019-11-14  9:53       ` Michael Chang
2019-11-15 11:42         ` Daniel Kiper
2019-11-19  8:34           ` Michael Chang
2020-03-03 16:59             ` Daniel Kiper [this message]
2020-03-04  7:58               ` Michael Chang

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=20200303165912.oqj6ac662sbl4y2q@tomti.i.net-space.pl \
    --to=dkiper@net-space.pl \
    --cc=MChang@suse.com \
    --cc=dave@jikos.cz \
    --cc=grub-devel@gnu.org \
    --cc=phcoder@gmail.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=terrelln@fb.com \
    /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.