From: Oleksandr <olekstysh@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <stefanos@xilinx.com>,
julien.grall@arm.com, JBeulich@suse.com,
andrew.cooper3@citrix.com
Subject: Re: [Xen-devel] [PATCH v2 03/10] xen: extend XEN_DOMCTL_memory_mapping to handle memory policy
Date: Wed, 15 May 2019 17:40:51 +0300 [thread overview]
Message-ID: <437edfef-00bf-fc90-3bf5-af8fa851fa3a@gmail.com> (raw)
Message-ID: <20190515144051.0BIN3n8iS8zeAwWmu9JFhknnIifymVLRGwsmH8u2o0c@z> (raw)
In-Reply-To: <1556658172-8824-3-git-send-email-sstabellini@kernel.org>
On 01.05.19 00:02, Stefano Stabellini wrote:
Hi, Stefano
> diff --git a/xen/common/domctl.c b/xen/common/domctl.c
> index 140f979..9f62ead 100644
> --- a/xen/common/domctl.c
> +++ b/xen/common/domctl.c
> @@ -928,6 +928,7 @@ long do_domctl(XEN_GUEST_HANDLE_PARAM(xen_domctl_t) u_domctl)
> unsigned long mfn_end = mfn + nr_mfns - 1;
> int add = op->u.memory_mapping.add_mapping;
> p2m_type_t p2mt;
> + uint32_t memory_policy = op->u.memory_mapping.memory_policy;
>
> ret = -EINVAL;
> if ( mfn_end < mfn || /* wrap? */
> @@ -958,9 +959,27 @@ long do_domctl(XEN_GUEST_HANDLE_PARAM(xen_domctl_t) u_domctl)
> if ( add )
> {
> printk(XENLOG_G_DEBUG
> - "memory_map:add: dom%d gfn=%lx mfn=%lx nr=%lx\n",
> - d->domain_id, gfn, mfn, nr_mfns);
> + "memory_map:add: dom%d gfn=%lx mfn=%lx nr=%lx cache=%u\n",
> + d->domain_id, gfn, mfn, nr_mfns, memory_policy);
>
> + switch ( memory_policy )
> + {
> +#ifdef CONFIG_ARM
> + case MEMORY_POLICY_ARM_MEM_WB:
> + p2mt = p2m_mmio_direct_c;
> + break;
> + case MEMORY_POLICY_ARM_DEV_nGRE:
> + p2mt = p2m_mmio_direct_dev;
> + break;
> +#endif
> +#ifdef CONFIG_X86
> + case MEMORY_POLICY_X86_UC:
> + p2mt = p2m_mmio_direct;
> + break;
> +#endif
> + default:
> + return -EOPNOTSUPP;
If I correctly understand the code, we can't just return an error here
(domctl_lock is taken, etc). Looks like we should store an error and
modify code to execute exit part.
--
Regards,
Oleksandr Tyshchenko
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-15 14:41 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 21:02 [PATCH v2 0/10] iomem memory policy Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-04-30 21:02 ` [PATCH v2 01/10] xen: add a p2mt parameter to map_mmio_regions Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-02 14:59 ` Jan Beulich
2019-05-02 14:59 ` [Xen-devel] " Jan Beulich
2019-05-02 18:49 ` Stefano Stabellini
2019-05-02 18:49 ` [Xen-devel] " Stefano Stabellini
2019-05-15 13:39 ` Oleksandr
2019-05-15 13:39 ` [Xen-devel] " Oleksandr
2019-04-30 21:02 ` [PATCH v2 02/10] xen: rename un/map_mmio_regions to un/map_regions Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-01 9:22 ` Julien Grall
2019-05-01 9:22 ` [Xen-devel] " Julien Grall
2019-06-17 21:24 ` Stefano Stabellini
2019-06-18 11:05 ` Julien Grall
2019-06-18 20:19 ` Stefano Stabellini
2019-05-02 15:03 ` Jan Beulich
2019-05-02 15:03 ` [Xen-devel] " Jan Beulich
2019-05-02 18:55 ` Stefano Stabellini
2019-05-02 18:55 ` [Xen-devel] " Stefano Stabellini
2019-04-30 21:02 ` [PATCH v2 03/10] xen: extend XEN_DOMCTL_memory_mapping to handle memory policy Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-02 15:12 ` Jan Beulich
2019-05-02 15:12 ` [Xen-devel] " Jan Beulich
2019-06-17 21:28 ` Stefano Stabellini
2019-06-18 8:59 ` Jan Beulich
2019-06-18 20:32 ` Stefano Stabellini
2019-06-18 23:15 ` Stefano Stabellini
2019-06-19 6:53 ` Jan Beulich
2019-05-07 16:41 ` Julien Grall
2019-05-07 16:41 ` [Xen-devel] " Julien Grall
2019-06-17 22:43 ` Stefano Stabellini
2019-06-18 11:13 ` Julien Grall
2019-05-15 14:40 ` Oleksandr [this message]
2019-05-15 14:40 ` Oleksandr
2019-04-30 21:02 ` [PATCH v2 04/10] libxc: introduce xc_domain_mem_map_policy Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-04-30 21:02 ` [PATCH v2 05/10] libxl/xl: add memory policy option to iomem Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-01 9:42 ` Julien Grall
2019-05-01 9:42 ` [Xen-devel] " Julien Grall
2019-06-17 22:32 ` Stefano Stabellini
2019-06-18 11:09 ` Julien Grall
2019-06-18 11:15 ` Julien Grall
2019-06-18 22:07 ` Stefano Stabellini
2019-06-18 22:20 ` Julien Grall
2019-06-18 22:46 ` Stefano Stabellini
2019-04-30 21:02 ` [PATCH v2 06/10] xen/arm: extend device_tree_for_each_node Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-07 17:12 ` Julien Grall
2019-05-07 17:12 ` [Xen-devel] " Julien Grall
2019-04-30 21:02 ` [PATCH v2 07/10] xen/arm: make process_memory_node a device_tree_node_func Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-01 9:47 ` Julien Grall
2019-05-01 9:47 ` [Xen-devel] " Julien Grall
2019-04-30 21:02 ` [PATCH v2 08/10] xen/arm: keep track of reserved-memory regions Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-01 10:03 ` Julien Grall
2019-05-01 10:03 ` [Xen-devel] " Julien Grall
2019-06-21 23:47 ` Stefano Stabellini
2019-05-07 17:21 ` Julien Grall
2019-05-07 17:21 ` [Xen-devel] " Julien Grall
2019-04-30 21:02 ` [PATCH v2 09/10] xen/arm: map reserved-memory regions as normal memory in dom0 Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-07 19:52 ` Julien Grall
2019-05-07 19:52 ` [Xen-devel] " Julien Grall
2019-04-30 21:02 ` [PATCH v2 10/10] xen/arm: add reserved-memory regions to the dom0 memory node Stefano Stabellini
2019-04-30 21:02 ` [Xen-devel] " Stefano Stabellini
2019-05-07 20:15 ` Julien Grall
2019-05-07 20:15 ` [Xen-devel] " Julien Grall
2019-05-10 20:51 ` Stefano Stabellini
2019-05-10 20:51 ` [Xen-devel] " Stefano Stabellini
2019-05-10 21:43 ` Julien Grall
2019-05-10 21:43 ` [Xen-devel] " Julien Grall
2019-05-11 12:40 ` Julien Grall
2019-05-11 12:40 ` [Xen-devel] " Julien Grall
2019-05-20 21:26 ` Stefano Stabellini
2019-05-20 21:26 ` [Xen-devel] " Stefano Stabellini
2019-05-20 22:38 ` Julien Grall
2019-05-20 22:38 ` [Xen-devel] " Julien Grall
2019-06-05 16:30 ` Julien Grall
2019-06-21 23:47 ` Stefano Stabellini
2019-05-16 16:52 ` [PATCH v2 0/10] iomem memory policy Oleksandr
2019-05-16 16:52 ` [Xen-devel] " Oleksandr
2019-06-21 23:48 ` Stefano Stabellini
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=437edfef-00bf-fc90-3bf5-af8fa851fa3a@gmail.com \
--to=olekstysh@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=stefanos@xilinx.com \
--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 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).