xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, jgross@suse.com,
	roger.pau@citrix.com, axboe@kernel.dk,
	xen-devel@lists.xensource.com
Subject: [GIT PULL] (xen) stable/for-jens-4.19 for 4.19..
Date: Mon, 27 Aug 2018 12:19:49 -0400	[thread overview]
Message-ID: <20180827161949.GG29187@char.us.oracle.com> (raw)

Hey Jens,

Would you be OK pulling the following branch:
 git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.19

which has a fix for flushing out persistent pages at a deterministic rate.

Thanks to the L1TF I did not manage to send this email until today - but
hopefully it won't be an issue to push it to Linus after -rc1?

It is based on your 'b86d865cb1ca (for-4.19/block) blkcg: Make blkg_root_lookup()
work for queues in bypass mode' branch.

Thank you! 

 Documentation/ABI/testing/sysfs-driver-xen-blkback |  10 ++
 drivers/block/xen-blkback/blkback.c                |  99 ++++++++++---------
 drivers/block/xen-blkback/common.h                 |  14 +--
 drivers/block/xen-blkfront.c                       | 110 ++++++++++++++++++---
 4 files changed, 163 insertions(+), 70 deletions(-)

Juergen Gross (5):
      xen/blkback: don't keep persistent grants too long
      xen/blkfront: cleanup stale persistent grants
      xen/blkfront: reorder tests in xlblk_init()
      xen/blkback: move persistent grants flags to bool
      xen/blkback: remove unused pers_gnts_lock from struct xen_blkif_ring

             reply	other threads:[~2018-08-27 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 16:19 Konrad Rzeszutek Wilk [this message]
2018-08-27 17:13 ` [GIT PULL] (xen) stable/for-jens-4.19 for 4.19 Jens Axboe

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=20180827161949.GG29187@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xensource.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 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).