I one up'd the answer above because, technically, it's correct on how to accomplish it. However, I would make the opposite recommendation. Meaning, I would recommend using linked servers for what you are doing. This is because it seams like you're asking the question about architecting Federated Servers using Distributed Partitioned Views techniques.
There are many rules and standards to implement when architecting. And it's true that Linked Servers shouldn't just be thrown into any mix to connect more than one server result sets. There are reasons to use objects and techniques for the right reasons.
Case in point, I successfully used Federated Servers/Distributed Views within a VLDB scenario that required multiple servers. That's what this technique is all about. It's advanced stuff, so fore-warned, but it answers exactly what you need to do to properly use Linked Servers for the Federated Servers/Distributed Views purpose.
I wanted one sever to be our current year of shipping data, and then the next 2-7 years on additional servers for archive. I needed to use multiple servers because of the volume of data and utilize the independent server resources for each query result set, depending on the year of the request. The technology of the Distributed View in the engine knew which server to go to and get the results. Because of the Check Constraints. Is it expensive, yes, does it work as is required, yes. Are linked servers stable, yes, but we had to account for the failure point. So, it isn't anything that can't be normally planned with similar requirements.
Make sure the Distributed Queries are properly architected and tested for performance and failure points.
In summary ... Possible, Yes; Do-able, Yes; recommend because it's needed for federated severs and distributed queries, Yes; HIGHLY recommend, not without thorough understanding and testing of the techniques.