All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
	Richard Henderson <rth@twiddle.net>,
	Alexander Graf <agraf@suse.de>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/2] s390x/kvm: legacy_s390_alloc() fixes
Date: Thu, 28 Jun 2018 17:22:15 +0200	[thread overview]
Message-ID: <20180628172215.142ed114.cohuck@redhat.com> (raw)
In-Reply-To: <20180628113817.30814-1-david@redhat.com>

On Thu, 28 Jun 2018 13:38:15 +0200
David Hildenbrand <david@redhat.com> wrote:

> Two patches for legacy_s390_alloc(), only relevant under old z/VM versions.

Those teddy bears are really looking a bit scruffy... but the patches
look sane.

> 
> Patch #1 is relevant when trying to allocate memory for more than one
> memory region. Patch #2 is only for completeness, to make it behave
> more similar to qemu_anon_ram_alloc().
> 
> David Hildenbrand (2):
>   s390x/kvm: legacy_s390_alloc() only supports one allocation
>   s390x/kvm: indicate alignment in legacy_s390_alloc()
> 
>  target/s390x/kvm.c | 15 +++++++++++++--
>  1 file changed, 13 insertions(+), 2 deletions(-)
> 

Thanks, applied.

      parent reply	other threads:[~2018-06-28 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 11:38 [Qemu-devel] [PATCH v1 0/2] s390x/kvm: legacy_s390_alloc() fixes David Hildenbrand
2018-06-28 11:38 ` [Qemu-devel] [PATCH v1 1/2] s390x/kvm: legacy_s390_alloc() only supports one allocation David Hildenbrand
2018-06-28 12:42   ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-06-28 11:38 ` [Qemu-devel] [PATCH v1 2/2] s390x/kvm: indicate alignment in legacy_s390_alloc() David Hildenbrand
2018-06-28 15:22 ` Cornelia Huck [this message]

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=20180628172215.142ed114.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.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.