grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: grub-devel@gnu.org
Subject: [PATCH v2 0/3] some disk reworking reposted
Date: Wed,  2 Mar 2016 00:14:09 +0000	[thread overview]
Message-ID: <1456877652-19389-1-git-send-email-leif.lindholm@linaro.org> (raw)

So, looking into this a bit more, thinking of how I could potentially
manage to sneak this into 2.02, and so on, I decided to rebase Andrei's
direct cache buffer patch onto the others.

Changes since v1:
- disk_malloc() function now used as default for all disks, rather than
  a runtime check for presence of disk-specific one
- adding Andrei's direct cache buffer use patch
  (obviously happy for this one to be treated separately, but made sense
   to include the rebased version with this posting)

Andrei Borzenkov (1):
  disk: read into cache directly

Leif Lindholm (2):
  disk: Add support for device-specific malloc function
  efidisk: implement alignment-respecting malloc function

 grub-core/disk/efi/efidisk.c |   8 ++++
 grub-core/kern/disk.c        | 105 +++++++++++++++++++++++++++----------------
 grub-core/lib/disk.c         |   6 +--
 include/grub/disk.h          |  16 ++++++-
 4 files changed, 92 insertions(+), 43 deletions(-)

-- 
2.1.4



             reply	other threads:[~2016-03-02  0:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  0:14 Leif Lindholm [this message]
2016-03-02  0:14 ` [PATCH v2 1/3] disk: Add support for device-specific malloc function Leif Lindholm
2016-03-02  0:14 ` [PATCH v2 2/3] efidisk: implement alignment-respecting " Leif Lindholm
2016-03-02  3:46   ` Andrei Borzenkov
2016-03-02 14:00     ` Leif Lindholm
2016-03-02  0:14 ` [PATCH v2 3/3] disk: read into cache directly Leif Lindholm
2016-03-02  0:22   ` Vladimir 'phcoder' Serbinenko
2016-03-02  3:46     ` Andrei Borzenkov
2016-03-02  9:55       ` Vladimir 'phcoder' Serbinenko
2016-03-03  0:04   ` Elliott, Robert (Persistent Memory)

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=1456877652-19389-1-git-send-email-leif.lindholm@linaro.org \
    --to=leif.lindholm@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).