All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andy Falanga (afalanga)" <afalanga@micron.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Addresses in PxCLB and PxCLBU
Date: Wed, 8 Jul 2015 14:20:47 +0000	[thread overview]
Message-ID: <559D31AE.5010609@micron.com> (raw)
In-Reply-To: <559CFF09.2040300@cogentembedded.com>

On 07/08/2015 04:44 AM, Sergei Shtylyov wrote:
> Hello.
>
> On 7/7/2015 2:41 AM, Andy Falanga (afalanga) wrote:
>
>> I'm working with the registers in an AHCI controller.  The memory
>> address contained in PxCLB and PxCLBU (if 64-bit addressing is
>> supported): what kind of address are they?
>
>    Apparently, physical. The hardware only operates on the physical 
> addresses.
>
>> Currently, when I get the
>> address and place it into a pointer of struct ahci_cmd_hdr and try to
>> dereference, my VM locks and then reboots.  What am I doing incorrectly?
>
>    You can't de-reference physical addresses.
>
>> Basically, I have this:
>
>> void __iomem * pbase = ahci_port_base((struct ata_port*));
>
>    Can't parse this.
>
>> struct ahci_cmd_hdr *cmd_hdr = NULL;
>
>> cmd_hdr = (struct ahci_cmd_hdr*)(u64)
>>      ((u64)(*(temp + PORT_LST_ADDR_HI)) << 32 | *temp);
>
>   temp?
>
>> pr_info("cmd_hdr is %p\n", cmd_hdr);
>> pr_info("cmd_hdr->opts is %d\n", cmd_hdr->opts);  /* opts is __le32 */
>
>> At the last line above my VM hangs and reboots.  The memory address is
>> something like 0x0000000037900000.  This address makes me think that I
>> simply can't dereference it but I'm quite new to this and I don't know
>> what I should do.  I'd appreciate any help even if that's a pointer (no
>> pun intended) to a more appropriate forum.
>
>    The corresponding virtual address seems to be contained in 
> ahci_port_priv::cmd_slot.
>
>> Thanks,
>> Andy
>

Thank you Sergei.  You are correct.  I'm finding that ditching old 
habits from user-land are hard to do.  I knew I needed to use things 
like ioread*/iowrite* when accessing those pointers but I just got stuck 
in a rhythm of "I've got a pointer now all I do is dereference ...." .  
Oh well.

Thanks much for getting back to me.

Andy

      reply	other threads:[~2015-07-08 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 23:41 Addresses in PxCLB and PxCLBU Andy Falanga (afalanga)
2015-07-08 10:44 ` Sergei Shtylyov
2015-07-08 14:20   ` Andy Falanga (afalanga) [this message]

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=559D31AE.5010609@micron.com \
    --to=afalanga@micron.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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.