All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: konrad@kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [RFC PATCHv1] serial: Support OXPCIe952 aka Oxford Semiconductor Ltd Device c138 (1415:c138)
Date: Tue, 4 Mar 2014 08:29:43 -0500	[thread overview]
Message-ID: <20140304132943.GA3449@localhost.localdomain> (raw)
In-Reply-To: <5315BF940200007800120CC2@nat28.tlf.novell.com>

On Tue, Mar 04, 2014 at 10:57:08AM +0000, Jan Beulich wrote:
> >>> On 04.03.14 at 11:36, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> 
> > On Mar 4, 2014 4:43 AM, Jan Beulich <JBeulich@suse.com> wrote:
> >>
> >> >>> On 04.03.14 at 03:01, Konrad Rzeszutek Wilk <konrad@kernel.org> wrote: 
> >> > @@ -325,11 +342,12 @@ static void __init ns16550_init_preirq(struct 
> > serial_port *port) 
> >> >  #ifdef CONFIG_X86 
> >> >          enum fixed_addresses idx = FIX_COM_BEGIN + (uart - ns16550_com); 
> >> >  
> >> > -        set_fixmap_nocache(idx, uart->io_base); 
> >> > +        set_fixmap_nocache(idx, uart->io_base + uart->offset); 
> >> >          uart->remapped_io_base = (void __iomem *)fix_to_virt(idx); 
> >> >          uart->remapped_io_base += uart->io_base & ~PAGE_MASK; 
> >>
> >> Don't you need to add in uart->offset here too?
> > 
> > The virtual address at that point already covers then BAR + offset.
> 
> Hardly: fix_to_virt() returns a page-aligned address, and anything
> that may affect the offset-in-page value needs to be taken into
> consideration in the right side expression of the +=.

Oh, this is not a offset-in-page (well, it is, but also past the first
page). In this case the offset ends up being BAR + 0x1000 + 0x200 * idx.
It is well past the first page.

Perhaps splitting it up in two offsets would be better?

	set_fixmap_nocache(idx, uart_io_base + uart->pfn_offset * PAGE_SIZE);
	uart->remapped_io_base = (void __iomem)*fix_to_virt(idx);
	uart->remapped_io_base += uart->io_base + uart->offset & ~PAGE_MASK;

And of course we make sure that offset is within 0->4096.

> 
> Jan
> 

  reply	other threads:[~2014-03-04 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 10:36 [RFC PATCHv1] serial: Support OXPCIe952 aka Oxford Semiconductor Ltd Device c138 (1415:c138) Konrad Rzeszutek Wilk
2014-03-04 10:57 ` Jan Beulich
2014-03-04 13:29   ` Konrad Rzeszutek Wilk [this message]
2014-03-04 15:39     ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2014-03-04  2:01 Konrad Rzeszutek Wilk
2014-03-04  3:17 ` Julien Grall
2014-03-04  9:43 ` Jan Beulich

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=20140304132943.GA3449@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=konrad@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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.