All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arianna Avanzini <avanzini.arianna@gmail.com>
To: Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Cc: Julien Grall <julien.grall@citrix.com>,
	paolo.valente@unimore.it, Keir Fraser <keir@xen.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Tim Deegan <tim@xen.org>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel@lists.xen.org,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	etrudeau@broadcom.com, Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Viktor Kleinik <viktor.kleinik@globallogic.com>
Subject: Re: [PATCH v10 00/12] Implement the XEN_DOMCTL_memory_mapping hypercall for ARM
Date: Wed, 20 Aug 2014 20:50:42 +0200	[thread overview]
Message-ID: <53F4EE02.9040500@gmail.com> (raw)
In-Reply-To: <CAH_mUMMRTyPNT-Zo-wG2e4YaVubJJzq5J7Z9oHWrmQTZbsoSiA@mail.gmail.com>

On 18/08/2014 21:50, Andrii Tseglytskyi wrote:
> Hi Arianna,
> 
> On Tue, Jul 29, 2014 at 1:11 AM, Arianna Avanzini
> <avanzini.arianna@gmail.com> wrote:
>> Hello,
>>
>> here I am finally with the tenth version of my implementation proposal for the
>> memory_mapping DOMCTL for the ARM architecture. As I did for the previous
>> versions, I'll try to keep this cover letter as short as I can by listing here
>> only the most relevant changes, while a more detailed description can be found
>> in the description and changelog that comes with each of the patches. More
>> detailed information about the patch series' genesis can be found in the last
>> full cover letter ([1]).
>> Please note that the second and third patches of the v9 series have been merged
>> by Ian Campbell ([2]) as they resulted in an interface change that would have
>> clashed with other upcoming merges.
>>
>> Patch 0001 has been fixed according to directives given by Julien Grall and
>> Ian Campbell; the main change is in the fact that now the ARM-related code
>> handling the removal of an I/O-memory mapping follows a behavior which matches
>> the one introduced for x86 by patch 0003: in case the given machine frame
>> number is mapped to an unexpected guest frame number, it emits a warning and
>> still destroys the mapping.
>>
>> Patch 0002 has been modified according to suggestions given by Ian Campbell;
>> now in case that the insertion of a new I/O-memory mapping fails (even if only
>> partially) the whole range is unmapped.
>>
>> Coding style issues existing in patch 0006 and pointed out by Jan Beulich have
>> been hopefully addressed here.
>>
>> A patch 0010 has been added that moves libxl's PCI-related macros, previously
>> kept in the libxl_pci.c file, to a header file.
>>
>> After some discussion involving Ian Campbell, Jan Beulich and Sander Eikelenboom
>> patch 0011 has been changed according to directives from Ian Campbell. Now the
>> I/O-memory areas needed to passthrough a VGA device in addition to PCI-related
>> ones are made accessible to any guest having gfx_passthru set to true in its
>> config and at least one passthru PCI device having a device class of 0x030000
>> (which should identify it as a VGA device).
>>
>> The code has again been tested on a cubieboard2, with Linux v3.15-rc3 as a dom0
>> and ERIKA Enterprise ([3]) as a domU. The x86 bits have been tested on an x86_64
>> machine with Linux 3.15.0-rc5 as both dom0 and domU.
>> Any feedback about this new version of the patchset is more than welcome,
>> Arianna
> 
> Do you have any public repo, where can I cherry - pick your latest
> patch series ?

Unfortunately as of now I don't have any. However (I'm hoping it helps) I will
be sending a new version of the patchset, updated for the latest head of the
development repository, within this week.

> This series is very useful for development we do in GlobalLogic - we
> have Android as domU, and we need iomem for such devices as GPU.
> For now we are using one of your previous series - is works fine for
> us. Platform is DRA7 (OMAP5)
> 

Thank you so much for providing feedback. Please do not hesitate to point out
any issue you might have.

> Also - I suppose - you are targeting this for Xen 4.5. Am I right ?
> 

Yes, you are right. I hope I'll be able to provide faster response to comments
and reviews in the near future.

Thank you,
Arianna



> Regards,
> Andrii
> 
> 
>> --
>> 2.0.3
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
> 
> 
> 


-- 
/*
 * Arianna Avanzini
 * avanzini.arianna@gmail.com
 * 73628@studenti.unimore.it
 */

  reply	other threads:[~2014-08-20 18:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 22:11 [PATCH v10 00/12] Implement the XEN_DOMCTL_memory_mapping hypercall for ARM Arianna Avanzini
2014-07-28 22:11 ` [PATCH v10 01/12] arch/arm: add consistency check to REMOVE p2m changes Arianna Avanzini
2014-07-29 11:55   ` Julien Grall
2014-07-29 12:01     ` Ian Campbell
2014-07-29 12:02     ` Andrew Cooper
2014-07-28 22:11 ` [PATCH v10 02/12] arch/arm: unmap partially-mapped I/O-memory regions Arianna Avanzini
2014-07-29 12:00   ` Julien Grall
2014-07-28 22:12 ` [PATCH v10 03/12] arch/x86: warn if to-be-removed mapping does not exist Arianna Avanzini
2014-07-28 22:12 ` [PATCH v10 04/12] arch/x86: cleanup memory_mapping DOMCTL Arianna Avanzini
2014-07-28 22:12 ` [PATCH v10 05/12] xen/common: add ARM stub for the function memory_type_changed() Arianna Avanzini
2014-07-28 22:12 ` [PATCH v10 06/12] xen/x86: factor out map and unmap from the memory_mapping DOMCTL Arianna Avanzini
2014-07-29  7:27   ` Jan Beulich
2014-07-29 12:02   ` Julien Grall
2014-07-28 22:12 ` [PATCH v10 07/12] xen/common: move the memory_mapping DOMCTL hypercall to common code Arianna Avanzini
2014-07-30 15:59   ` Julien Grall
2014-07-28 22:12 ` [PATCH v10 08/12] tools/libxl: parse optional start gfn from the iomem config option Arianna Avanzini
2014-08-04 13:39   ` Julien Grall
2014-07-28 22:12 ` [PATCH v10 09/12] tools/libxl: handle the iomem parameter with the memory_mapping hcall Arianna Avanzini
2014-07-28 22:12 ` [PATCH v10 10/12] tools/libxl: move PCI-related macros in a header file Arianna Avanzini
2014-07-28 22:12 ` [PATCH v10 11/12] tools/libxl: explicitly grant access to needed I/O-memory ranges Arianna Avanzini
2014-07-30 11:33   ` Ian Campbell
2014-07-28 22:12 ` [PATCH v10 12/12] xen/common: do not implicitly permit access to mapped I/O memory Arianna Avanzini
2014-07-29  7:29   ` Jan Beulich
2014-08-18 19:50 ` [PATCH v10 00/12] Implement the XEN_DOMCTL_memory_mapping hypercall for ARM Andrii Tseglytskyi
2014-08-20 18:50   ` Arianna Avanzini [this message]
2014-08-20 19:15     ` Andrii Tseglytskyi
2014-08-21 15:43       ` Andrii Tseglytskyi
2014-08-22 14:25         ` Arianna Avanzini
2014-08-22 18:27           ` Andrii Tseglytskyi
2014-08-22 18:36             ` Arianna Avanzini
2014-08-22 19:31               ` Andrii Tseglytskyi
2014-08-22 23:51                 ` Stefano Stabellini
2014-08-23 12:07                   ` Arianna Avanzini
2014-08-23 17:36                     ` Andrii Tseglytskyi

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=53F4EE02.9040500@gmail.com \
    --to=avanzini.arianna@gmail.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=dario.faggioli@citrix.com \
    --cc=etrudeau@broadcom.com \
    --cc=julien.grall@citrix.com \
    --cc=keir@xen.org \
    --cc=paolo.valente@unimore.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=viktor.kleinik@globallogic.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 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.