All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, kvm@vger.kernel.org
Cc: lvivier@redhat.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH 4/4] lib/x86/vm: enable malloc and friends
Date: Tue, 1 Nov 2016 15:48:54 +0100	[thread overview]
Message-ID: <cbc9f10b-73f6-19a5-bf2a-60c4d3d51ab3@redhat.com> (raw)
In-Reply-To: <1477939906-28802-5-git-send-email-drjones@redhat.com>



On 31/10/2016 19:51, Andrew Jones wrote:
> We've had malloc, calloc, free, and memalign available for quite a
> while, and arm and powerpc make use of them. x86 hasn't yet, but
> let's give it the option. arm and powerpc use the early_alloc_ops,
> built on phys_alloc, but x86 already has virtual memory management,
> so we can build on that instead.

What are your plans for using them?  vmalloc imposes a pretty large
alignment and is quite different from early_alloc_ops, so I'm not sure
it's a good idea to conflate the two into the same high-level API.

Thanks,

Paolo

  reply	other threads:[~2016-11-01 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 18:51 [kvm-unit-tests PATCH 0/4] x86: enable malloc and friends Andrew Jones
2016-10-31 18:51 ` [kvm-unit-tests PATCH 1/4] lib/alloc: improve robustness Andrew Jones
2016-11-02  6:08   ` Thomas Huth
2016-11-02 10:24     ` Andrew Jones
2016-10-31 18:51 ` [kvm-unit-tests PATCH 2/4] x86: lib/alloc: move heap management to common code Andrew Jones
2016-11-02  6:14   ` Thomas Huth
2016-10-31 18:51 ` [kvm-unit-tests PATCH 3/4] lib/alloc: return a zeroed page from alloc_page Andrew Jones
2016-11-01 14:47   ` Paolo Bonzini
2016-10-31 18:51 ` [kvm-unit-tests PATCH 4/4] lib/x86/vm: enable malloc and friends Andrew Jones
2016-11-01 14:48   ` Paolo Bonzini [this message]
2016-11-01 15:49     ` Andrew Jones
2016-11-01  8:58 ` [kvm-unit-tests PATCH 0/4] x86: " Andrew Jones

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=cbc9f10b-73f6-19a5-bf2a-60c4d3d51ab3@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --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.