All of lore.kernel.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: John David Anglin <dave.anglin@bell.net>
Cc: Tom Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-parisc@vger.kernel.org
Subject: Re: HP-UX for C8000
Date: Sun, 1 Oct 2017 10:11:42 -0400	[thread overview]
Message-ID: <77C25382-EF4C-4AE5-9860-A23777D29B1E@bell.net> (raw)
In-Reply-To: <F6CD5540-CC99-4D7B-8625-3757D8F05BC6@bell.net>

On 2017-10-01, at 9:20 AM, John David Anglin wrote:

>> 
>> Does anybody know HP-UX ? Could I mmap the register of quicksilver
>> and dump it from user space ?
> 
> Manpage for mmap says:
> 
>      The mmap() function is supported for regular files.  Support for any
>      other type of file is unspecified.
> 
> If there is a device, possibly one can use dd.

There are also /dev/mem and /dev/kmem:

 mem(7)                                                               mem(7)

 NAME
      mem - main memory

 DESCRIPTION
      mem is a special file that is an image of the main memory of the
      computer.  It may be used, for example, to examine and patch the
      system.

      Byte addresses in mem are interpreted as physical memory addresses.
      References to non-existent locations cause errors to be returned.

      File kmem is the same as mem except that kernel virtual memory rather
      than physical memory is accessed.  Please refer to kmem(7) for
      information about ioctl operations that are supported on /dev/kmem.
...

 NAME
      kmem - perform I/O on kernel memory based on symbol name.

Dave
--
John David Anglin	dave.anglin@bell.net




  reply	other threads:[~2017-10-01 14:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30 15:25 HP-UX for C8000 Tom Bogendoerfer
2017-09-30 17:34 ` John David Anglin
2017-10-01 11:46   ` Tom Bogendoerfer
2017-10-01 13:20     ` John David Anglin
2017-10-01 14:11       ` John David Anglin [this message]
2017-10-01 14:47     ` John David Anglin
2017-10-01 15:02     ` John David Anglin
2017-10-06 14:39       ` Tom Bogendoerfer
2017-10-08 16:22         ` John David Anglin
2017-10-08 16:41           ` John David Anglin
2017-10-09 15:34             ` Helge Deller
2017-10-09 16:05               ` Tom Bogendoerfer
2017-10-09 17:40                 ` John David Anglin
2017-10-09 16:30               ` John David Anglin
2017-10-09 17:41                 ` Tom Bogendoerfer
2017-10-09 22:22                   ` John David Anglin
2017-10-10  0:56                   ` John David Anglin
2017-10-10 18:46                     ` Tom Bogendoerfer
2017-10-10 22:06                       ` John David Anglin
2017-11-02  1:57                         ` Brendan Horan
2017-11-02 14:25                           ` John David Anglin
2017-11-02 16:38                             ` Tom Bogendoerfer
2017-11-02 17:45                               ` John David Anglin

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=77C25382-EF4C-4AE5-9860-A23777D29B1E@bell.net \
    --to=dave.anglin@bell.net \
    --cc=linux-parisc@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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.