xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: mail fetch <fetchmail.0104@gmail.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel@lists.xen.org, julien.grall@citrix.com,
	stefano.stabellini@citrix.com
Subject: Re: Issue with ARM: Network doesn't work in the guest
Date: Wed, 13 Nov 2013 16:43:25 +0000	[thread overview]
Message-ID: <5283AC2D.9080601@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1311081137500.26077@kaball.uk.xensource.com>



On 11/11/2013 01:13 PM, Stefano Stabellini wrote:
> On Thu, 7 Nov 2013, Julien Grall wrote:
>> On 11/06/2013 10:12 AM, Stefano Stabellini wrote:
>>> On Wed, 30 Oct 2013, mail fetch wrote:
>>>> 2013/10/29, mail fetch <fetchmail.0104@gmail.com>:
>>>>> Hi all,
>>>>>
>>>>> I just saw a know bug from wiki that network doesn't work in guest in
>>>>> arndale board :
>>>>>
>>>>> Network doesn't work in the guest
>>>>>
>>>>> Contact: julien.grall@citrix.com
>>>>> Status: In progress
>>>>> Description: Network doesn't work in the guest when an ehternet cable is
>>>>> plugged
>>>>> References: http://pastebin.com/gEP3HdCg
>>>>>
>>>>> What's the latest status?
>>>>>
>>>>> best regards
>>>>> Mail
>>>>>
>>>>
>>>> Any comments?
>>>
>>> Sorry for the late reply. Usually we respond pretty quickly but you
>>> caught us between Xen Developer Summit and Linaro Connect: most Xen
>>> hackers were traveling. In fact Julien Grall is still AFK and he
>>> is the one that knows the answer.
>>>
>>> I think that the 1:1 workaround in dom0 (that is having pseudo-physical
>>> addresses == physical addresses for dom0) should fix it. Give a look at
>>
>> Actually it's not enough. The problem is because when the balloon driver will
>> release a page, Xen will populate with a new allocated page. So it will break
>> the 1:1 Workaround.
>> The commit eee34edcd1daecb70560dfe23009af2e65f7d26d on my tree in xenbits
>> (git://xenbits.xen.org/people/julieng/xen-unstable.git) aims to fix this
>> issue.
>> I will try to remember to update the wiki page monday when I will come back to
>> the office.
>>
>> Stefano: A couple of weeks ago, you told me you plan to rework this commit for
>> the swiotlb, is it still relevant?
>
> After looking at this a bit more, I think that your workaround is
> reasonable and less fragile than my original idea based on modifying the
> Linux balloon driver. I think that it just needs to be cleaned a bit,
> see appended comments.

Thanks. I will rework the patch and send it soon.

-- 
Julien Grall

      reply	other threads:[~2013-11-13 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF9N9CME-b_8wpNyBT00b4GQ-PQ2XzuKXS4TQLf-pyBhFLBrNA@mail.gmail.com>
2013-10-30 11:52 ` Issue with ARM: Network doesn't work in the guest mail fetch
2013-11-06 18:12   ` Stefano Stabellini
2013-11-08  7:03     ` Julien Grall
2013-11-11 13:13       ` Stefano Stabellini
2013-11-13 16:43         ` Julien Grall [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=5283AC2D.9080601@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=fetchmail.0104@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).