Displaying 20 results from an estimated 202 matches for "smaps".
Did you mean:
maps
2019 Jan 07
3
[RFC PATCH V3 0/5] Hi:
On 2019/1/7 ??11:28, Michael S. Tsirkin wrote:
> On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote:
>> On 2019/1/3 ??4:47, Michael S. Tsirkin wrote:
>>> On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote:
>>>> This series tries to access virtqueue metadata through kernel virtual
>>>> address instead of copy_user() friends since they had
2019 Jan 07
3
[RFC PATCH V3 0/5] Hi:
On 2019/1/7 ??11:28, Michael S. Tsirkin wrote:
> On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote:
>> On 2019/1/3 ??4:47, Michael S. Tsirkin wrote:
>>> On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote:
>>>> This series tries to access virtqueue metadata through kernel virtual
>>>> address instead of copy_user() friends since they had
2019 Jan 07
2
[RFC PATCH V3 0/5] Hi:
On 2019/1/3 ??4:47, Michael S. Tsirkin wrote:
> On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote:
>> This series tries to access virtqueue metadata through kernel virtual
>> address instead of copy_user() friends since they had too much
>> overheads like checks, spec barriers or even hardware feature
>> toggling.
> Will review, thanks!
> One questions
2019 Jan 07
2
[RFC PATCH V3 0/5] Hi:
On 2019/1/3 ??4:47, Michael S. Tsirkin wrote:
> On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote:
>> This series tries to access virtqueue metadata through kernel virtual
>> address instead of copy_user() friends since they had too much
>> overheads like checks, spec barriers or even hardware feature
>> toggling.
> Will review, thanks!
> One questions
2013 Jan 28
1
SMAP feature causing kernel alignment faults due to setting EFLAGS.AC
This appears to be the case in the recent messages in Debian bug #660425
[0] (thread starts at [1] and continues at [2]).
SMAP uses EFLAGS.AC in kernel mode to indicate whether accesses to
usermode pages should fault or not, which gets confused because under
64-bit Xen kernel == ring3. The obvious fix would be to clear SMAP from
the cpuid features (probably in kernel as well as hypervosr) but
2018 Dec 26
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote:
>
> On 2018/12/25 ??8:50, Michael S. Tsirkin wrote:
> > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
> > > On 2018/12/25 ??2:10, Michael S. Tsirkin wrote:
> > > > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
> > > > > On 2018/12/14 ??8:36, Michael S. Tsirkin
2018 Dec 26
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote:
>
> On 2018/12/25 ??8:50, Michael S. Tsirkin wrote:
> > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
> > > On 2018/12/25 ??2:10, Michael S. Tsirkin wrote:
> > > > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
> > > > > On 2018/12/14 ??8:36, Michael S. Tsirkin
2018 Dec 25
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
>
> On 2018/12/25 ??2:10, Michael S. Tsirkin wrote:
> > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
> > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote:
> > > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
> > > > > On 2018/12/13 ??11:44, Michael S. Tsirkin
2018 Dec 25
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
>
> On 2018/12/25 ??2:10, Michael S. Tsirkin wrote:
> > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
> > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote:
> > > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
> > > > > On 2018/12/13 ??11:44, Michael S. Tsirkin
2018 Dec 30
1
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Thu, Dec 27, 2018 at 05:39:21PM +0800, Jason Wang wrote:
>
> On 2018/12/26 ??11:02, Michael S. Tsirkin wrote:
> > On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote:
> > > On 2018/12/25 ??8:50, Michael S. Tsirkin wrote:
> > > > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
> > > > > On 2018/12/25 ??2:10, Michael S. Tsirkin
2019 Jan 07
0
[RFC PATCH V3 0/5] Hi:
On Mon, Jan 07, 2019 at 11:53:41AM +0800, Jason Wang wrote:
>
> On 2019/1/7 ??11:28, Michael S. Tsirkin wrote:
> > On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote:
> > > On 2019/1/3 ??4:47, Michael S. Tsirkin wrote:
> > > > On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote:
> > > > > This series tries to access virtqueue metadata
2003 Jul 28
1
ASUS P4BGL-MX hangs
Hi there,
sorry for rather long mail. Two verbose dmesgs and `pciconf -vl` outputs
attached.
trying to set up new machine based on ASUS P4BGL-MX motherboard, I'd
encountered hangs after detecting pcib1 (ICH2). MB has rl 8100 ethernet chip
onboard.
This is for 4.8-R; however, machine hangs in very similar way also with 4.4-R
and 5.1-R.
Matrix of hangs:
Onboard Ether External Ether Result
2018 Dec 27
0
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On 2018/12/26 ??11:02, Michael S. Tsirkin wrote:
> On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote:
>> On 2018/12/25 ??8:50, Michael S. Tsirkin wrote:
>>> On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
>>>> On 2018/12/25 ??2:10, Michael S. Tsirkin wrote:
>>>>> On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
2018 Dec 26
0
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On 2018/12/25 ??8:50, Michael S. Tsirkin wrote:
> On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote:
>> On 2018/12/25 ??2:10, Michael S. Tsirkin wrote:
>>> On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
>>>> On 2018/12/14 ??8:36, Michael S. Tsirkin wrote:
>>>>> On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
2008 May 14
1
RELENG_6 regression: panic: vm_fault on nofault entry, addr: c8000000
Hi,
there's a regression going from 6.2 to 6.3, where it will panic upon
booting the kernel within vm_fault. This problem has been discussed
before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of
May.
It affects multiple (but identical) systems, here's an verbose boot
leading to the panic. Please note that 6.2 was running fine on these
machines, they also boot
2009 Aug 06
2
robots.txt
Hi all,
I have again noticed that the wiki does not really show up in search
results and wonder if it has any impact that robots.txt on
wiki.centos.org is empty.
Perhaps it should at least contain User-agent: * ?
Best Regards
Marcus
2018 Dec 24
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
>
> On 2018/12/14 ??8:36, Michael S. Tsirkin wrote:
> > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
> > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote:
> > > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote:
> > > > > It was noticed that the copy_user()
2018 Dec 24
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
>
> On 2018/12/14 ??8:36, Michael S. Tsirkin wrote:
> > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
> > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote:
> > > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote:
> > > > > It was noticed that the copy_user()
2017 May 05
2
Memory leak in samba-ad-dc on 4.5.x not related to aio?
...0, Sven Schwedas wrote:
> On 2017-05-05 10:09, Volker Lendecke wrote:
> > On Fri, May 05, 2017 at 09:42:47AM +0200, Sven Schwedas via samba wrote:
> >>> root 9988 0.8 59.4 1571936 606488 ? S Apr26 114:41 /usr/sbin/samba
> >
> > Can you post /proc/9988/smaps somewhere?
>
> Sure, http://up.tao.at/-0242609d03e69298bb27155078663d51/smaps.9988.txt
Ok, it's actually the heap. I was hoping that it's a mmap'ed ldb. So
we do have something fishy going on that. Sorry, I con't have an easy
recipe.
Volker
--
SerNet GmbH, Bahnhofsallee 1...
2018 Dec 14
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
>
> On 2018/12/13 ??11:44, Michael S. Tsirkin wrote:
> > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote:
> > > It was noticed that the copy_user() friends that was used to access
> > > virtqueue metdata tends to be very expensive for dataplane
> > > implementation like vhost since it