All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Nazar <nazard.michi@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Big Endian fix patch
Date: Wed, 28 Jul 2010 11:52:00 -0400	[thread overview]
Message-ID: <4C505220.20101@gmail.com> (raw)
In-Reply-To: <20100728150037.GC2632@caffeine.csclub.uwaterloo.ca>

  On 2010-07-28 11:00 AM, Lennart Sorensen wrote:
>
> OK, no idea how I got by without that.  It is currently working for me.
> Weird.
>
> I only use raid1 of course, so that is all I tested with.
>
It only mattered for multipath. Which is a kind of raid1 setup. Grub 
doesn't handle it too well since the underlying device is the same and 
has the same disk number. Before we'd overwrite the old path with the 
last path found and incorrectly increase nr_devs. With my patch we just 
ignore additional drives. So we'll die if we lose the path while booting 
but otherwise it'll find at least one of the paths.
>> - Fix the ofdisk_hash system. We weren't making a copy of the devpath so
>> never found the cached item again.
> Could this have anything to do with why I can't see disks without
> devaliases assigned?
>
No. This would only affect the disk cache subsystem (since the hash 
struct pointer was used as the disk id) and we'd be comparing the 
devpath with random memory.
>
> QEMU/openbios has many bugs unfortunately.  If I could make any sense
> of the code I would try to fix some of them, but I simply can't follow
> that code.
>
I've got a basic idea how it all hangs together internally and I started 
to fix a few things in OpenBios but discovered the current source 
doesn't work with QEMU 0.12.5. "boot" stopped working and if I used 
"load" it started to work then complained that it was trying to 
overwrite OpenBios. Since I have no idea how the memory is supposed to 
be laid out I kinda backed away. Besides, Forth is not my first choice 
of languages to figure out.

> I will give this patch a try on top of mine then and see how it behaves.
>
Thanks for testing,
Doug



  parent reply	other threads:[~2010-07-28 15:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  1:00 Big Endian fix patch (was: Re: Couple more fixes for Linux raid metadata 1.x support) Doug Nazar
2010-07-27 15:26 ` Lennart Sorensen
2010-07-27 23:58   ` Big Endian fix patch Doug Nazar
2010-07-28 14:52     ` Lennart Sorensen
2010-07-28 15:29       ` Doug Nazar
2010-07-28  8:51   ` Doug Nazar
2010-07-28 15:00     ` Lennart Sorensen
2010-07-28 15:51       ` Lennart Sorensen
2010-07-28 16:30         ` Doug Nazar
2010-07-28 17:01           ` Lennart Sorensen
2010-07-28 17:12             ` Doug Nazar
2010-07-28 17:40               ` Lennart Sorensen
2010-07-28 17:42               ` Lennart Sorensen
2010-07-28 17:52                 ` Lennart Sorensen
2010-07-28 18:17                   ` Doug Nazar
2010-07-28 18:49                     ` Lennart Sorensen
2010-07-28 20:10                       ` Doug Nazar
2010-07-28 22:25                         ` Lennart Sorensen
2010-07-28 20:46                       ` Doug Nazar
2010-07-29 15:30                         ` Lennart Sorensen
2010-07-28 18:01                 ` Doug Nazar
2010-07-28 18:50                   ` Lennart Sorensen
2010-07-28 15:52       ` Doug Nazar [this message]
2010-07-28 15:55         ` Lennart Sorensen
2010-09-13 19:54     ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4C505220.20101@gmail.com \
    --to=nazard.michi@gmail.com \
    --cc=grub-devel@gnu.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.