Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Apr 2017 03:49:50 +0000
From:      Dexuan Cui <decui@microsoft.com>
To:        Konstantin Belousov <kostikbel@gmail.com>
Cc:        "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, Sepherosa Ziehau <sephe@freebsd.org>, Hongjiang Zhang <honzhan@microsoft.com>
Subject:   RE: svn commit: r316767 - head/sys/amd64/amd64
Message-ID:  <HK2P15301MB000343EE50BDA160907A4C68BF180@HK2P15301MB0003.APCP153.PROD.OUTLOOK.COM>
In-Reply-To: <20170418134556.GY1788@kib.kiev.ua>
References:  <201704131549.v3DFnt9I004050@repo.freebsd.org> <HK2P15301MB00033BEA7B656EBCD3BDFC5CBF190@HK2P15301MB0003.APCP153.PROD.OUTLOOK.COM> <20170418134556.GY1788@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
> From: Konstantin Belousov
> > It looks memory allocated by bus_dmamem_alloc() and malloc()
> > is not executable now.
> >
> > What else can we use?
> > I guess we can only use contigmalloc() or kmem_malloc() to
> > get a page that can be executable and use vtophys() to get its
> > physical address?
> Yes, the kmem_malloc() is considered to be a suitable substitution for
> regular malloc(9) if the executable mapping is needed.  See r317072
> for a similar fix for the same issue.

Thanks, kib!
We have fixed Hyper-V drivers with kmem_malloc().

Thanks,
-- Dexuan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?HK2P15301MB000343EE50BDA160907A4C68BF180>