From owner-freebsd-current@freebsd.org  Tue Apr  5 18:16:05 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7267AB03215
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  5 Apr 2016 18:16:05 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com
 [IPv6:2607:f8b0:400e:c03::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4E79F1C15;
 Tue,  5 Apr 2016 18:16:05 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: by mail-pa0-x231.google.com with SMTP id td3so15319802pab.2;
 Tue, 05 Apr 2016 11:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc; bh=Yv3FvvChwB4wnRYsyJbOBRQ+tosCE3p/l/hvYlKG/Ic=;
 b=dysurvngqe7aasaM5QFd9jnbkn9bA1MKEjZInREmDZ8AOIInOmQqZOBNsCKIbgKyJX
 OMJuzRZmxW8Voyk/7PV4iXmjeEdfIsN5aSPKEtKWdykTEqDGokXXhmKqqJsxC0kXbgbH
 V2SFGnNrIfauk5j+CSr05WqgG+9y6XXLEI67X+1naYvShGdiibGAvG8D7WztnJF9AK/8
 VF4Ew8eLF1eHtMYXkJfm16sMWi7/zhwq9fr1pMRG7zXwtT6uWzu8Ys2QSXCBcrEw7juc
 1QEkHWVbErOM1miOHRONvO+VP45zHZdhz8SXq7vFcAV2HKs0j64nJQaL20blPssWFLxs
 Zq9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:cc;
 bh=Yv3FvvChwB4wnRYsyJbOBRQ+tosCE3p/l/hvYlKG/Ic=;
 b=afhlWcFgIXZUj73KpPszgiMWLEL9GeciNIOh47dLggezBXLGYtbRq6UvTh96bHCk+6
 S71xo6nnsq3y/A7nWDirqVgIjSfcx6FNKlkHdvacpQJ6eC3ikR5L0XJp0p1g1u1EJei+
 xywrgChgD0QX7IyAAniKvwcB/5OB4S9HcIMaBdwmbg3V3Sq47pbtErVjjsO6pCSYjGyv
 7BgCGZwDGjbtV/iFy/Mg213VBz54M+J2WiEtvDffmPSzfqqxb2sARjPrDv9M51gyjYN3
 QhPNKqpU6LHpw+P8XeZTr077jcm5lrCdklw7ja9qA38msDMHpYFhADu5IcN1aoFSIgKd
 ejxQ==
X-Gm-Message-State: AD7BkJK1eF+YpqeWIyGMSMe4knONdyC6DdG1RWfdPjSPiDBnPm8Yq+OfnTCVYX/6/5C6jIAjM9eogB7UOk0WYQ==
MIME-Version: 1.0
X-Received: by 10.107.150.2 with SMTP id y2mr18299725iod.113.1459880164533;
 Tue, 05 Apr 2016 11:16:04 -0700 (PDT)
Received: by 10.107.153.206 with HTTP; Tue, 5 Apr 2016 11:16:04 -0700 (PDT)
In-Reply-To: <20160405061013.GE1741@kib.kiev.ua>
References: <CA+hQ2+iU4odjhaNicFA4QjvSZR2OZOOy+Fu4LTqsibdoK4M8zg@mail.gmail.com>
 <9376230.YZMFsgSvTf@ralph.baldwin.cx>
 <CAFMmRNzpOgBPsBezOyUZ_=qjCywfADx8MuJWdaWb_D+7UCmi7Q@mail.gmail.com>
 <5009932.qXoZ6E4rhX@ralph.baldwin.cx>
 <20160405061013.GE1741@kib.kiev.ua>
Date: Tue, 5 Apr 2016 14:16:04 -0400
Message-ID: <CAFMmRNy=dZSq4is+zPJhVV0n0gnJNNExUh04iA7AGACkvyDuYg@mail.gmail.com>
Subject: Re: accessing a PCIe register from userspace through kmem or other
 ways ?
From: Ryan Stone <rysto32@gmail.com>
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: John Baldwin <jhb@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.21
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 18:16:05 -0000

On Tue, Apr 5, 2016 at 2:10 AM, Konstantin Belousov <kostikbel@gmail.com>
wrote:

> The mmap(2) interface to /dev/mem did not have the issue ever.  The problem
> was only with the read(2)/write(2) accesses.
>

I mis-remembered my situation.  I was performing a read on /dev/mem rather
than reading through a mmap.  Thanks for clearing this up.