mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	boris.ostrovsky@oracle.com
Subject: [GIT PULL] xen: fixes for 5.0-rc3
Date: Fri, 18 Jan 2019 10:57:13 +0100	[thread overview]
Message-ID: <20190118095713.3192-1-jgross@suse.com> (raw)

Linus,

Please git pull the following tag:

 git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.0-rc3-tag

xen: fixes for 5.0-rc3

It contains:
- Several fixes for the Xen pvcalls drivers (1 fix for the backend and
  8 for the frontend).
- A fix for a rather longstanding bug in the Xen sched_clock()
  interface which led to weird time jumps when migrating the system.
- A fix for avoiding accesses to x2apic MSRs in Xen PV guests.


Thanks.

Juergen

 arch/x86/xen/enlighten_pv.c      |   5 +-
 arch/x86/xen/time.c              |  12 +++--
 drivers/xen/events/events_base.c |   2 +-
 drivers/xen/pvcalls-back.c       |   9 ++--
 drivers/xen/pvcalls-front.c      | 104 ++++++++++++++++++++++++++++-----------
 5 files changed, 90 insertions(+), 42 deletions(-)

Juergen Gross (1):
      xen: Fix x86 sched_clock() interface for xen

Stefano Stabellini (5):
      pvcalls-front: read all data before closing the connection
      pvcalls-front: don't try to free unallocated rings
      pvcalls-front: properly allocate sk
      pvcalls-front: don't return error when the ring is full
      pvcalls-back: set -ENOTCONN in pvcalls_conn_back_read

Talons Lee (1):
      always clear the X2APIC_ENABLE bit for PV guest

Wen Yang (2):
      pvcalls-front: Avoid get_free_pages(GFP_KERNEL) under spinlock
      pvcalls-front: fix potential null dereference

YueHaibing (1):
      xen/pvcalls: remove set but not used variable 'intf'

             reply	other threads:[~2019-01-18  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  9:57 Juergen Gross [this message]
2019-01-18 18:05 ` pr-tracker-bot

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=20190118095713.3192-1-jgross@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xen-devel@lists.xenproject.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

all inboxes | Powered by JetHome®